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: Mon, 23 Feb 2009 00:17:00 -0000 [thread overview]
Message-ID: <20090222194316.GA21483@caradoc.them.org> (raw)
In-Reply-To: <1235102359.4719.3.camel@localhost.localdomain>
On Fri, Feb 20, 2009 at 09:29:19AM +0530, Vinay Sridhar wrote:
> I placed a break on "add_thread" as you suggested. It doesn't seem to be
> hit at all, for any of the threads.
> BTW, I'm using GNU gdb (GDB) 6.8.50.20090216.
At the time of the original error, are all your threads in the thread
list? GDB's internal thread_list variable, not the result of "info
threads", which will check for new threads.
If they are, and they do not have private info set, what added them to
the thread list? I missed one function; maybe they were added by
add_thread_silent?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-22 19:43 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
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 [this message]
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=20090222194316.GA21483@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