Bug 20278 - Corefile debugging should be able report crashed thread
Summary: Corefile debugging should be able report crashed thread
Status: RESOLVED FIXED
Alias: None
Product: gdb
Classification: Unclassified
Component: corefiles (show other bugs)
Version: unknown
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-20 15:44 UTC by award
Modified: 2023-03-29 14:12 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description award 2016-06-20 15:44:20 UTC 
After selecting a corefile to debug a message is outputted in the form of "Program terminated with signal <signal>, <reason>." But there is no indication of which thread crashed. This indication is clearly in the corefile. Would be useful to have a command that reports which thread crashed, along with the signal and the reason.
Comment 1 Tom Tromey 2023-03-29 14:12:34 UTC 
I think in the cases where it can, gdb selects the crashing thread.
In other cases it just may not know.
I'm going to close this bug; but if it's still an issue for you,
we can reopen it with more info about the particular platform.