Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [non-stop] 08/10 linux native support
Date: Thu, 10 Jul 2008 18:01:00 -0000	[thread overview]
Message-ID: <200807101901.23598.pedro@codesourcery.com> (raw)
In-Reply-To: <20080710171518.GA19554@caradoc.them.org>

On Thursday 10 July 2008 18:15:18, Daniel Jacobowitz wrote:
> On Thu, Jul 10, 2008 at 04:27:49PM +0100, Pedro Alves wrote:
> > > This (the thread_db_attach_lwp version) looks reasonable to me.  Ugly,
> > > but reasonable.  Why do we need the parent's data?
> >
> > Due to this:
> >
> >  (gdb) r&
> >  Starting program: /home/pedro/gdb/tests/threads32
> >  (gdb) [Thread debugging using libthread_db enabled]
> >  [New Thread 0xf7df0b90 (LWP 24154)]
> >  [New Thread 0xf75efb90 (LWP 24155)]
> >  info threads
> >    3 Thread 0xf75efb90 (LWP 24155)  (running)
> >    2 Thread 0xf7df0b90 (LWP 24154)  (running)
> >  * 1 LWP 24151  (running)
>
> Why didn't this thread get identified at the shared library event,
> when libthread_db was loaded?  It already existed by then, being the
> main thread.

Because we hit this in find_new_threads_callback:

  if (ti.ti_tid == 0)
    {
      /* A thread ID of zero means that this is the main thread, but
	 glibc has not yet initialized thread-local storage and the
	 pthread library.  We do not know what the thread's TID will
	 be yet.  Just enable event reporting and otherwise ignore
	 it.  */

#0  find_new_threads_callback (th_p=0xffb316c4, data=0x0) at ../../src/gdb/linux-thread-db.c:1011
#1  0xf7dfbb59 in ?? () from /lib32/libthread_db.so.1
#2  0xf7dfbc11 in td_ta_thr_iter () from /lib32/libthread_db.so.1
#3  0x080a8dec in thread_db_find_new_threads () at ../../src/gdb/linux-thread-db.c:1044
#4  0x080a8371 in check_for_thread_db () at ../../src/gdb/linux-thread-db.c:665
#5  0x080a83af in thread_db_new_objfile (objfile=0x84a6cf8) at ../../src/gdb/linux-thread-db.c:679
...

That's from here:

649       /* Now attempt to open a connection to the thread library.  */
650       err = td_ta_new_p (&proc_handle, &thread_agent);
651       switch (err)
652         {
653         case TD_NOLIBTHREAD:
654           /* No thread library was detected.  */
655           break;
656
657         case TD_OK:
658           printf_unfiltered (_("[Thread debugging using libthread_db enabled]\n"));
659
660           /* The thread library was detected.  Activate the thread_db target.  */
661           push_target (&thread_db_ops);
662           using_thread_db = 1;
663
664           enable_thread_event_reporting ();
665           thread_db_find_new_threads ();
666           break;

-- 
Pedro Alves


  reply	other threads:[~2008-07-10 18:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 21:10 Pedro Alves
2008-06-25 21:17 ` Daniel Jacobowitz
2008-06-25 22:03   ` Pedro Alves
2008-06-25 22:12     ` Pedro Alves
2008-06-25 22:52       ` Daniel Jacobowitz
2008-06-25 23:08     ` Daniel Jacobowitz
2008-07-02  3:35       ` Pedro Alves
2008-07-07 18:20         ` Daniel Jacobowitz
2008-07-09  3:25           ` Michael Snyder
2008-07-09  3:47             ` Daniel Jacobowitz
2008-07-09  3:55               ` Michael Snyder
2008-07-09  7:55                 ` Mark Kettenis
2008-07-09  7:56             ` Mark Kettenis
2008-07-10 15:28           ` Pedro Alves
2008-07-10 17:15             ` Daniel Jacobowitz
2008-07-10 18:01               ` Pedro Alves [this message]
2008-07-10 19:59                 ` Daniel Jacobowitz
2008-07-10 21:51                   ` Pedro Alves
2008-07-10 22:15                     ` Daniel Jacobowitz
2008-07-10 23:01                       ` Pedro Alves

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=200807101901.23598.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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