crash in __nptl_death_event

Carlos O'Donell
Thu Aug 28 13:17:00 GMT 2008

On Thu, Aug 28, 2008 at 6:07 AM, Jiri Olsa <> wrote:
> Also I've never saw gdb message:
> Program received signal 0, Signal 0.

This looks like a bug in gdb or glibc's nptl libthread_db. Normally
signal 0 means "continue program", but in this case your program
caught the signal? Have you set any signal handling? What does info
signals show?

Have you tried building gdb from fsf cvs head and seeing if you can
reproduce the failure?


More information about the Libc-help mailing list