From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Albert Fu <quarkverse@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Program terminated by SIGTRAP in gdb
Date: Fri, 16 Jan 2009 02:06:00 -0000 [thread overview]
Message-ID: <8ac60eac0901151805w1953e06do991af229cdccb5a2@mail.gmail.com> (raw)
In-Reply-To: <966c7c700901141637g49f2bafcj6e95c60c80227eba@mail.gmail.com>
On Wed, Jan 14, 2009 at 4:37 PM, Albert Fu <quarkverse@gmail.com> wrote:
> Program received signal SIGTRAP, Trace/breakpoint trap.
This is happening because GDB did not attach some of the application
threads.
The most frequent causes are:
- libpthread.so.0 is stripped
What does the command below produce:
nm /lib/libpthread.so.0 | egrep '_version|threads_events'
- libpthread.so.0 does not match in version libthread_db.so.1
This may happen if you build your own glibc, but don't install
all the pieces of it.
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-01-16 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 0:37 Albert Fu
2009-01-15 2:08 ` teawater
2009-01-16 2:06 ` Paul Pluzhnikov [this message]
2009-01-16 19:05 ` Albert Fu
2009-01-16 20:13 ` Paul Pluzhnikov
[not found] ` <966c7c700901161513o6bca18dbx5ad35a1924b41130@mail.gmail.com>
2009-01-16 23:34 ` 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=8ac60eac0901151805w1953e06do991af229cdccb5a2@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=quarkverse@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