Open Bug 1934315 Opened 1 year ago Updated 1 year ago

JSRuntime::atExit routines run in such a state that segmentation faults don't print anything

Categories

(Core :: JavaScript Engine, task, P3)

Product:
Core
Component:
JavaScript Engine
Type:
task

Tracking

()

People

(Reporter: mgaudet, Unassigned)

References

(Blocks 1 open bug)

Details

For Bug 1934123 I wrote a little stats gathering patch that used cx->runtime()->atexit to dump the results

the problem is however, I lost a bunch of time debugging it because it was silently sigsev'ing, and I didn't notice the exit code in my terminal... just the lack of printing.

This has something to do with the state of the WasmTrap handler when the atexit runs.

Blocks: sm-runtime
Severity: -- → N/A
Priority: -- → P3
Summary: JSRuntime::atExit routines run in such a state that sementation faults don't print anything → JSRuntime::atExit routines run in such a state that segmentation faults don't print anything
You need to log in before you can comment on or make changes to this bug.