Ludovic Courtès, le mar. 17 nov. 2020 14:55:32 +0100, a ecrit: > Samuel Thibault <samuel.thiba...@gnu.org> skribis: > > > Ludovic Courtès, le mar. 17 nov. 2020 10:57:43 +0100, a ecrit: > >> I’ve noticed that I’d always get “broken” stack traces in GDB when (1) > >> attaching to a program suspended by /servers/crash-suspend, (2) > >> examining a core dump, or (3) spawning a program in GDB and examining it > >> after it’s received an unhandled signal like SIGILL.
Ah, in all case you mean when receiving an unhandled signal? I see that happen indeed. > I get pretty back traces until the program gets an unhandled signal, > AFAICT. This makes me think it could have something to do with how GDB > obtains thread state info for suspended threads. Probably, yes. Samuel
