Re: gdb/2248: Threads terminated by SIGTRAP in gdbserver (powerpc)

[Gregoire Banderet <Gregoire dot Banderet at ge dot com>]

The following reply was made to PR gdb/2248; it has been noted by GNATS.

From: Gregoire Banderet <Gregoire.Banderet@ge.com>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: gdb/2248: Threads terminated by SIGTRAP in gdbserver (powerpc)
Date: Tue, 10 Apr 2007 16:15:26 +0200

 Daniel Jacobowitz wrote:
 > On Wed, Apr 04, 2007 at 03:25:05PM -0000, gregoire.banderet@ge.com wrote:
 >> I try to to do some remote debugging on my ppc platform.
 >> I downloaded lates gdb sources (release 6.6) and cross-compiled gdbserver for powerpc-wrs-linux-gnu. I've of course also compiled a gdb for my target.
 >> Everything's fien for apps that are not multi-threaded.
 >> But for multi-threaded (NPTL) apps, there is no way to stop in a specific thread. In fact gdb always sees only one thread (the main one), thread info reports only one thread.
 >> If I set a breakpoint in code executed by a thread, gdbserver reports:
 >> Child terminated with signal = 5
 > 
 > Please see the latest version of the GDB manual, which has a section
 > on this:
 >   http://sourceware.org/gdb/
 > 
 > You probably need to set solib-absolute-prefix, which is called
 > sysroot in the latest development version of GDB.
 
 I tried both: "set solib-absolute-prefix" and "--with-sysroot" at 
 compile time. I still have the SIGTRAP and gdb still sees only the main 
 thread.
 Do I need a debug version of pthread lib in my sysroot ?