From: "Paul Pluzhnikov" <ppluzhnikov@google.com>
To: "Andrew Lofthouse" <loftyhauser@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: "Cannot find new threads" on Fedora 9, but not on CentOS 5 (?)
Date: Tue, 28 Oct 2008 00:42:00 -0000 [thread overview]
Message-ID: <8ac60eac0810271741h135f077bj2c3fcd7391e89ed7@mail.gmail.com> (raw)
In-Reply-To: <49065BBD.3050800@gmail.com>
On Mon, Oct 27, 2008 at 5:24 PM, Andrew Lofthouse <loftyhauser@gmail.com> wrote:
> I'm trying to debug an application that throws a SEGFAULT in a shared
> library. On Fedora 9 (and on Ubuntu 8.04), I get the following error:
>
> [Thread debugging using libthread_db enabled]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
> Cannot find new threads: generic error
Please see:
http://sourceware.org/ml/gdb/2008-08/msg00208.html
for possible reasons.
> However, when using CentOS 5, the debugging session seems to work fine and
> gives the following output:
>
> [Detaching after fork from child process 1973]
> [Detaching after fork from child process 1992]
> [Detaching after fork from child process 2004]
>
> Program received signal SIGSEGV, Segmentation fault.
>
> etc, etc--basically gdb works and tells me where the segmentation fault is.
>
> So, I know that Fedora 9/Ubuntu 8.04 use gdb version 6.8, while CentOS 5
> uses version 6.5. Why can an earlier version of gdb work fine, while the
> later version doesn't work? What can I do so that the later version works?
This is most likely result of "pilot error" (stripping
libpthread.so.0, or incomplete installation of glibc), and has
nothing to do with actual version of GDB.
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2008-10-28 0:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 0:25 Andrew Lofthouse
2008-10-28 0:42 ` Paul Pluzhnikov [this message]
[not found] ` <4906615E.50606@gmail.com>
[not found] ` <8ac60eac0810271836saf8c28pb1392b77c7926be0@mail.gmail.com>
2008-10-29 1:16 ` Andrew Lofthouse
2008-10-29 1:52 ` Daniel Jacobowitz
2008-10-29 2:21 ` Paul Pluzhnikov
2008-10-30 1:11 ` Andrew Lofthouse
2008-10-30 1:30 ` Paul Pluzhnikov
2008-11-01 2:30 ` Andrew Lofthouse
2008-11-01 6:47 ` Paul Pluzhnikov
2008-11-01 15:29 ` Andrew Lofthouse
2008-11-01 21:41 ` Paul Pluzhnikov
2008-11-02 12:54 ` Andrew Lofthouse
2008-11-04 0:50 ` Tom Tromey
2008-12-12 22:50 ` Tom Tromey
2008-12-12 23:04 ` Daniel Jacobowitz
2008-12-12 23:30 ` Tom Tromey
2008-12-18 19:36 ` Michael Snyder
2008-12-12 23:06 ` 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=8ac60eac0810271741h135f077bj2c3fcd7391e89ed7@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=loftyhauser@gmail.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