Segfault when using try/catch in a test

[volodymyrprokopyuk]

How can we reproduce the crash?

Hi,

I think that the segfault is due to using the try/catch in a test. I use HardHat with ethers.js and the bun test runner to test Solidity contracts.

  test("Revert with insufficient funds", async () => {
    const [token, owner, acc1] = await loadFixture(contractAndAccounts)
    try {
      await token.connect(acc1).transfer(owner, 1n)
    } catch (e) {
      console.log(e)
    }
  })

The full example is at https://github.com/volodymyrprokopyuk/problem-solving/blob/master/solidity/tests/Token.test.js

Thank you for doing the exceptional work!

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.31 (e448c4c) on linux x86_64_baseline [TestCommand]

Segmentation fault at address 0x00000020

• ZigGlobalObject.cpp:308: formatStackTraceToJSValue
• ZigGlobalObject.cpp:2642: Zig::jsFunctionDefaultErrorPrepareStackTrace
• 1 unknown/js code
• ld-temp.o:0: llint_call_javascript
• ld-temp.o:0: JSC::Interpreter::executeCall
• ZigGlobalObject.cpp:336: formatStackTraceToJSValue
• ZigGlobalObject.cpp:697: computeErrorInfoWithPrepareStackTrace
• ZigGlobalObject.cpp:737: computeErrorInfoToJSValue

Features: jsc, no_avx2, transpiler_cache, tsconfig