Program terminated by SIGTRAP in gdb

Paul Pluzhnikov ppluzhnikov@google.com
Fri Jan 16 02:06:00 GMT 2009


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



More information about the Gdb mailing list