Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Laurent Carlier <lordheavym@gmail.com>
To: gdb@sourceware.org
Subject: Re: Cannot find new threads: generic error
Date: Sun, 31 Aug 2008 02:30:00 -0000	[thread overview]
Message-ID: <200808300213.57239.lordheavym@gmail.com> (raw)
In-Reply-To: <200808281553.37056.lordheavym@gmail.com>

Le Thursday 28 August 2008 15:53:36 Laurent Carlier, vous avez écrit :
> Sorry if i break the thread, i find these mails wihile seraching about this
> problem.
>
> I got the same problem when running gdb with a program using dlopen() too
> and under debian sid (the same problem occur under the last ubuntu release)
>
> I've filled a bug report on debian bug tracking system:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496494
>
> So the output from gdb is:
> lordh@debian:~/gb2projets/TunnelSDL$ gdb gbx3
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html> This is free software: you are free to
> change and redistribute it. There is NO WARRANTY, to the extent permitted
> by law.  Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu"...
> (gdb) run -p
> Starting program: /usr/local/bin/gbx3 -p
> [Thread debugging using libthread_db enabled]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
> Cannot find new threads: generic error
> (gdb) bt
> #0  0x00007ff0873787b7 in dl_open_worker () from
> /lib64/ld-linux-x86-64.so.2 #1  0x00007ff087374366 in _dl_catch_error ()
> from /lib64/ld-linux-x86-64.so.2 #2  0x00007ff0873780eb in _dl_open () from
> /lib64/ld-linux-x86-64.so.2 #3  0x00007ff086ee0fbb in dlopen_doit () from
> /lib/libdl.so.2
> #4  0x00007ff087374366 in _dl_catch_error () from
> /lib64/ld-linux-x86-64.so.2 #5  0x00007ff086ee136c in _dlerror_run () from
> /lib/libdl.so.2
> #6  0x00007ff086ee0f21 in dlopen@@GLIBC_2.2.5 () from /lib/libdl.so.2
> #7  0x0000000000420685 in LIBRARY_load (lib=0x15dd400) at gbx_library.c:468
> #8  0x0000000000441f4b in COMPONENT_load (comp=0x15dd3a0) at
> gbx_component.c:250
> #9  0x0000000000441b22 in COMPONENT_load_all () at gbx_component.c:110
> #10 0x000000000041fd5f in PROJECT_load () at gbx_project.c:456
> #11 0x0000000000432d2e in init (file=0x446378 ".") at gbx.c:85
> #12 0x00000000004332ef in main (argc=1, argv=0x7fff8f582968) at gbx.c:299
> (gdb)
>
> >>  [Thread debugging using libthread_db enabled]
> >>  Error while reading shared library symbols:
> >>  Cannot find new threads: generic error
> >>
> >> I'm using kernel 2.6.24 on a recent debian/unstable libc6.
> >>
> >> Where does that error come from?
> >
> >This is most often the result of either
> >A. mismatch between libc.so.6 and libthread_db.so.1, or
> >B. libpthread.so.0 being stripped.
> >
> >What does 'nm /lib/libpthread.so.0 | grep _version' say?
>
> The output is:
> lordh@debian:~$ nm /lib/libpthread.so.0 | grep _version
> 0000000000010420 r nptl_version
>
> Regards,

I've find a workaround, i've link the debugging app with libpthread and now gdb 
feels happy, and i can run it with gdb !

Does anybody got an idea how to fix definitivly this problem ?

Thank for your advices.

Regards,
Laurent Carlier


  reply	other threads:[~2008-08-30  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 17:48 Laurent Carlier
2008-08-31  2:30 ` Laurent Carlier [this message]
2008-08-31  5:05   ` Paul Pluzhnikov
2008-08-31 14:07     ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2008-08-17 23:07 Russell Shaw
2008-08-18 13:16 ` Paul Pluzhnikov

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=200808300213.57239.lordheavym@gmail.com \
    --to=lordheavym@gmail.com \
    --cc=gdb@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