From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: How to indicate failing thread in core file.
Date: Mon, 12 May 2003 21:48:00 -0000 [thread overview]
Message-ID: <17d101c318d0$3107ba00$0202040a@catdog> (raw)
I'm fixing up our core-file reading stuff in elf.c and trying to see how to
indicate the thread that failed. I'm only setting the core_signal and
core_lwpid on the thread that got the signal but that doesn't seem to be
doing the trick. How does gdb know which thread was currently running when
the core was generated?
cheers,
Kris
reply other threads:[~2003-05-12 21:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='17d101c318d0$3107ba00$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).