[Bug gdb/23616] Unknown signal error from gdb when stepping over musl libc function call using SIGSYNCCALL

bugdal at aerifal dot cx sourceware-bugzilla@sourceware.org
Tue Oct 15 19:48:00 GMT 2019


Rich Felker <bugdal at aerifal dot cx> changed:

           What    |Removed                     |Added
                 CC|                            |bugdal at aerifal dot cx

--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> ---
Rather than hard-coding implementation internals (which will change; SIGTIMER
is slated to be removed at some point and the others moved to free up a slot),
a clean patch should just handle "unknown" signals in some safe way (i.e. not
get stuck on them). Do you understand the mechanism of how this problem is even
happening? Presumably it's a weird mixup between host and target -- it should
be possible to debug local glibc-linked inferiors with a musl-hosted gdb, or
vice versa, so I don't understand how ideas of the semantics of
implementation-internal signals are coming into this.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Gdb-prs mailing list