1317802 - don't stop for SIGSYS in .gdbinit

Status: RESOLVED FIXED

(Core :: General, defect)

Description

[Nathan Froyd [:froydnj]]

The sandboxing code generates this signal nowadays, which makes
debugging with tools like rr quite frustrating.

Comment 1

[Nathan Froyd [:froydnj]]

Attachment: don't stop for SIGSYS in .gdbinit

Picking jld because he probably understands the sandboxing code and how this
would interact with rr?  Feel free to redirect.

Comment 2

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

Comment on attachment 8811024 [details] [diff] [review]
don't stop for SIGSYS in .gdbinit

Seems like a good idea — for all practical purposes, SIGSYS is now an implementation detail / expected side effect of calls like open(), and unless you're working on sandboxing or debugging a sandboxing issue you won't want to stop on it.

Printing the signal could have some value, but usually it will just be confusing and annoying, especially because gdb will stop and prompt after every screenful of messages, so turning that off is fine too.

Comment 3

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

As for rr, there were some issues with using the SIGSYS handler to polyfill syscalls with other syscalls but they've been fixed, so as far as I know it should now be faithfully reproducing the SIGSYS-related irritation level of a regular debugging session (modulo sometimes changing the direction of time).

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/fa4c2f76351d
don't stop for SIGSYS in .gdbinit; r=jld

Comment 5

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/fa4c2f76351d