From: Jim Blandy <jimb@redhat.com>
To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
Cc: <gdb@sources.redhat.com>
Subject: Re: multi-thread debugging not working
Date: Thu, 18 Jul 2002 14:55:00 -0000 [thread overview]
Message-ID: <npznwog0r0.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <007f01ea8a71$cce46880$9a0a0109@zhangl>
"Lucy Zhang" <lucyz@uclink4.berkeley.edu> writes:
> Great thank you. One more question though. Right now I only have one NOTE
> segment which contain one of each types of note (prstatus, prpsinfo,
> taskstruct). When I add the new note structs for each thread, should I add
> in into the same NOTE segment after my current single thread structs? Which
> is what readelf -n seems to be suggesting.
> OR should I create a new NOTE segment, and add it in there like the
> following? Which way does GDB prefer?
I don't think GDB will care. The core file I've seen has them all in
one NOTE segment.
If you end up trying to debug this, some starting points: the code
which actually parses the NOTE segment is elfcore_read_notes, in
bfd/elf.c. It turns the prstatus notes into `.reg/PID' sections. The
GDB code which then consumes those sections is add_to_thread_list in
corelow.c.
next prev parent reply other threads:[~2002-07-18 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 13:16 problem loading libpthread.so Lucy Zhang
2002-07-16 13:23 ` Daniel Jacobowitz
2002-07-16 16:54 ` multi-thread debugging not working Lucy Zhang
2002-07-16 18:41 ` Daniel Jacobowitz
2002-07-17 15:08 ` Jim Blandy
2002-07-17 16:30 ` Lucy Zhang
2002-07-18 14:55 ` Jim Blandy [this message]
2002-07-16 19:05 Lucy Zhang
2002-07-16 19:08 ` Daniel Jacobowitz
2002-07-17 12:54 ` Lucy Zhang
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=npznwog0r0.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=lucyz@uclink4.berkeley.edu \
/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