This is the mail archive of the
mailing list for the GDB project.
Re: looking for gdb's help
- From: Simon Marchi <simark at simark dot ca>
- To: XXX <710492440 at qq dot com>, bug-gdb <bug-gdb at gnu dot org>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 14 May 2019 12:17:49 -0400
- Subject: Re: looking for gdb's help
- References: <tencent_BFF0537BE500EBD744189A00B384F5C26E06@qq.com>
On 2019-05-14 3:26 a.m., XXX wrote:
> i have a question about gdb debugging. while a signal cause a core dump, how can i get which thread cause the signal. the _siginfo only records the pid, not thread id. while debugging the core file, the current thread is not the thread which cause the core signal.
> i am looking for your reply, thank you!
Is this core dump created by the Linux kernel? IIRC, the Linux kernel typically
places the signalled thread first in the list of of threads, such that when I
open a core dump in GDB, thread 1 is usually the one that caused the problem.