* Debugging crashes when backtrace is not useful
@ 2024-05-20 19:03 Eli Zaretskii
2024-05-20 19:28 ` Hannes Domani
0 siblings, 1 reply; 2+ messages in thread
From: Eli Zaretskii @ 2024-05-20 19:03 UTC (permalink / raw)
To: gdb
Hi,
An Emacs user on Windows reported frequent crashes, but when run from
GDB, the relevant thread shows backtrace of zero:
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x0000000000000000 in ?? ()
What can be done to try to understand what code produces this, and
why?
TIA
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Debugging crashes when backtrace is not useful
2024-05-20 19:03 Debugging crashes when backtrace is not useful Eli Zaretskii
@ 2024-05-20 19:28 ` Hannes Domani
0 siblings, 0 replies; 2+ messages in thread
From: Hannes Domani @ 2024-05-20 19:28 UTC (permalink / raw)
To: gdb, Eli Zaretskii
Am Montag, 20. Mai 2024 um 21:03:55 MESZ hat Eli Zaretskii via Gdb <gdb@sourceware.org> Folgendes geschrieben:
> Hi,
>
> An Emacs user on Windows reported frequent crashes, but when run from
> GDB, the relevant thread shows backtrace of zero:
>
> (gdb) bt
> #0 0x0000000000000000 in ?? ()
> #1 0x0000000000000000 in ?? ()
>
> What can be done to try to understand what code produces this, and
> why?
>
> TIA
Looks like it could have been this bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=30255
Did they try with gdb-14, which has this one fixed?
Hannes
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-05-20 19:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-05-20 19:03 Debugging crashes when backtrace is not useful Eli Zaretskii
2024-05-20 19:28 ` Hannes Domani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).