From: Daniel Jacobowitz <drow@false.org>
To: Vinay Sridhar <vinay@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, luisgpm@linux.vnet.ibm.com
Subject: Re: [RFC][Patch] Fix gdb failure to access tls data for parent thread
Date: Wed, 04 Feb 2009 13:29:00 -0000 [thread overview]
Message-ID: <20090204132851.GA9935@caradoc.them.org> (raw)
In-Reply-To: <200901091416.10563.vinay@linux.vnet.ibm.com>
On Fri, Jan 09, 2009 at 02:16:09PM +0530, Vinay Sridhar wrote:
> The reason for this is gdb does not fill in the private field of the
> thread_info structure of the parent thread. The below patch sets up
> this private field before the child threads are added to gdb's list.
The private info is set in attach_thread. That is supposed to be
called for every thread; how did you get a thread on the thread list
that did not have this routine called? A breakpoint on add_thread
and add_thread_with_info will probably figure this out.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-04 13:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 8:47 Vinay Sridhar
2009-02-04 13:29 ` Daniel Jacobowitz [this message]
2009-02-11 8:33 ` Vinay Sridhar
2009-02-11 15:53 ` Daniel Jacobowitz
2009-02-12 5:45 ` Vinay Sridhar
2009-02-16 3:19 ` Daniel Jacobowitz
2009-02-16 15:04 ` Vinay Sridhar
2009-02-16 15:20 ` Daniel Jacobowitz
2009-02-17 7:01 ` Vinay Sridhar
2009-02-17 16:20 ` Daniel Jacobowitz
2009-02-20 8:31 ` Vinay Sridhar
2009-02-23 0:17 ` Daniel Jacobowitz
2009-02-23 9:20 ` Vinay Sridhar
2009-02-23 16:10 ` Daniel Jacobowitz
2009-02-24 7:11 ` Pedro Alves
2009-02-24 13:33 ` Vinay Sridhar
2009-02-24 13:39 ` Vinay Sridhar
2009-02-24 17:16 ` Daniel Jacobowitz
2009-02-24 18:52 ` Pedro Alves
2009-02-24 18:58 ` Pedro Alves
2009-02-25 18:28 ` Vinay Sridhar
2009-02-27 21:49 ` Pedro Alves
2009-02-24 10:57 ` Vinay Sridhar
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=20090204132851.GA9935@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=vinay@linux.vnet.ibm.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