Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Doug Evans <dje@google.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	        "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix for gdb.threads/staticthreads.exp failure on Linux
Date: Thu, 16 Jul 2009 20:54:00 -0000	[thread overview]
Message-ID: <8ac60eac0907161338l74de06daj35ce093343a865dc@mail.gmail.com> (raw)
In-Reply-To: <8ac60eac0907161248yf46afa8o2abe3b36d0f6d599@mail.gmail.com>

On Thu, Jul 16, 2009 at 12:48 PM, Paul Pluzhnikov<ppluzhnikov@google.com> wrote:

> gdb-glibc-2.7   test-glibc-2.3.6: KFAIL:
> gdb-glibc-2.3.6 test-glibc-2.3.6: no failures

Why should "how gdb built" matter here?
Because the test suite doesn't set libthread-db-search-path.

When I set verbose on, for KFAIL I see this:

  (gdb) run
  Starting program: staticthreads
  Trying host libthread_db library: libthread_db.so.1.
  Host libthread_db.so.1 resolved to: /lib/libthread_db.so.1.
  td_ta_new failed: versions of libpthread and libthread_db do not match
  Trying host libthread_db library: libthread_db.so.1.
  Host libthread_db.so.1 resolved to: /lib/libthread_db.so.1.
  td_ta_new failed: versions of libpthread and libthread_db do not match

  Breakpoint 1, main (argc=1, argv=0x7fffffffdaa8) at staticthreads.c:51
  51        pthread_attr_init (&attr);

When I set libthread-db-search-path correctly for the target program,
then I see the same behavior with gdb-glibc-2.7 and gdb-glibc-2.3.6:

# before the patch:

  (gdb) run
  Starting program: staticthreads
  Trying host libthread_db library: /usr/glibc-2.3.6/lib64/libthread_db.so.1.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/usr/glibc-2.3.6/lib64/libthread_db.so.1".
  find_new_threads_callback: cannot get thread info: generic error
  (gdb) c
  Continuing.
  Cannot execute this command while the selected thread is running.

     # no further debugging possible

# after the patch:

  (gdb) run
  Starting program: staticthreads
  Trying host libthread_db library "/usr/glibc-2.3.6/lib64/libthread_db.so.1".
  [Thread debugging using libthread_db enabled]
  Warning: thread_db_find_new_threads_silently:
find_new_threads_callback: cannot get thread info: generic error
  Warning: guessed host libthread_db library
"/usr/glibc-2.3.6/lib64/libthread_db.so.1".
  Using host libthread_db library "/usr/glibc-2.3.6/lib64/libthread_db.so.1".
  [New Thread 0x693860 (LWP 10575)]
  [Switching to Thread 0x693860 (LWP 10575)]

  Breakpoint 1, main (argc=1, argv=0x7fffffffdab8) at
../../../src/gdb/testsuite/gdb.threads/staticthreads.c:51
  51        pthread_attr_init (&attr);

-- 
Paul Pluzhnikov


  reply	other threads:[~2009-07-16 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 22:22 Paul Pluzhnikov
2009-06-15 18:39 ` Paul Pluzhnikov
2009-06-22 16:10   ` Paul Pluzhnikov
2009-06-22 18:10     ` Michael Snyder
2009-06-22 20:21       ` Paul Pluzhnikov
2009-06-29 14:36         ` Paul Pluzhnikov
2009-07-09  6:36           ` Paul Pluzhnikov
2009-07-16  2:42         ` Doug Evans
2009-07-16  2:43           ` Doug Evans
2009-07-16 20:45           ` Paul Pluzhnikov
2009-07-16 20:54             ` Paul Pluzhnikov [this message]
2009-07-16 21:16             ` Doug Evans

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=8ac60eac0907161338l74de06daj35ce093343a865dc@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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