[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Broken stack traces on crashed programs
|
From: |
Ludovic Courtès |
|
Subject: |
Re: Broken stack traces on crashed programs |
|
Date: |
Tue, 17 Nov 2020 14:55:32 +0100 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Hi!
Samuel Thibault <samuel.thibault@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.
>>
>> 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?
Yes.
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.
> (meaning: no, I don't have such kind of issue with gdb 9.2 in debian)
(Same with GDB 10.1.)
It could be that we’re missing a libc patch that Debian has, or (more
likely) that we’re miscompiling something on the way (this is all
cross-compiled from x86_64-linux-gnu).
To be continued…
Ludo’.