SEA tests run into SIGSEGV during SEA execution

[joyeecheung]

From the latest reliability report, it seems many of the SEA tests are running into SIGSEGV on Windows/macOS/RHEL when executing the generated SEA.

nodejs/reliability#718

Some ideas about investigating into the flakes:

1. Use spawnSyncAndExitWithoutError() for better output
2. Use NODE_DEBUG_NATIVE=SEA to log the deserialization
3. Log onto the machines to check out what's going on

cc @nodejs/single-executable

[richardlau]

Crashed on GHA too on main: https://github.com/nodejs/node/actions/runs/6892307239

test-linux: test/sequential/test-single-executable-application-snapshot-and-code-cache.js#L64
--- stderr ---
[process 207047]: --- stderr ---

[process 207047]: --- stdout ---

[process 207047]: status = null, signal = SIGSEGV
/home/runner/work/node/node/test/common/child_process.js:86
    throw new Error(`${failures.join('\n')}`);
    ^

Error: - process terminated with status null, expected 0
- process terminated with signal SIGSEGV, expected null
    at logAndThrow (/home/runner/work/node/node/test/common/child_process.js:86:11)
    at expectSyncExit (/home/runner/work/node/node/test/common/child_process.js:91:5)
    at spawnSyncAndExitWithoutError (/home/runner/work/node/node/test/common/child_process.js:125:10)
    at Object.<anonymous> (/home/runner/work/node/node/test/sequential/test-single-executable-application-snapshot-and-code-cache.js:64:3)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Module._load (node:internal/modules/cjs/loader:1023:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49

Node.js v22.0.0-pre
Command: out/Release/node --test-reporter=spec --test-reporter-destination=stdout --test-reporter=./tools/github_reporter/index.js --test-reporter-destination=stdout /home/runner/work/node/node/test/sequential/test-single-executable-application-snapshot-and-code-cache.js

[joyeecheung]

Not sure if this is the same as the "all failed on PPC" that we are seeing. I'll open another PR to at least log some stuff.

Seperately it would be great if we can install a built-in SIGSEGV handler to dump the stack trace..