Bug 1866396 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Please check your GDB configuration. You might find that this "crash" is purely GDB stopping in a signal and Firefox itself works correctly.
Revision 1 by
on 
Please check your GDB configuration. You might find that this "crash" is purely GDB stopping in a signal and Firefox itself works correctly.

Starting gdb via mach will load build/.gdbinit which contains:

``handle SIGSYS noprint nostop pass``

See also https://firefox-source-docs.mozilla.org/contributing/debugging/debugging_firefox_with_gdb.html#i-keep-getting-a-sig32-or-sigsegv-in-js-jit-code-under-gdb-even-though-there-is-no-crash-when-gdb-is-not-attached-how-do-i-fix-it
Revision 2 by
on 
Please check your GDB configuration. You might find that this "crash" is purely GDB stopping in a signal and Firefox itself works correctly.

Starting gdb via mach will load ``build/.gdbinit`` which contains:

``handle SIGSYS noprint nostop pass``

See also https://firefox-source-docs.mozilla.org/contributing/debugging/debugging_firefox_with_gdb.html#i-keep-getting-a-sig32-or-sigsegv-in-js-jit-code-under-gdb-even-though-there-is-no-crash-when-gdb-is-not-attached-how-do-i-fix-it

Back to Bug 1866396 Comment 7