Bug 20278

Summary:	Corefile debugging should be able report crashed thread
Product:	gdb	Reporter:	award
Component:	corefiles	Assignee:	Not yet assigned to anyone <unassigned>
Status:	RESOLVED FIXED
Severity:	normal	CC:	tromey
Priority:	P2
Version:	unknown
Target Milestone:	---
Host:		Target:
Build:		Last reconfirmed:

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.