[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
Thu Oct 17 02:08:00 GMT 2019


--- Comment #3 from Rich Felker <bugdal at aerifal dot cx> ---
Reportedly this fixes the issue. I don't entirely understand the mechanism, but
it seems plausible that this is closer to correct.


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

More information about the Gdb-prs mailing list