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. > > At best I can see the backtrace of the msg thread, the other ones are > all question-marky:
Silly question, but still important to ask: did you build with -g? (meaning: no, I don't have such kind of issue with gdb 9.2 in debian) Samuel
