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

Daniel Jacobowitz drow@false.org
Sun Apr 8 21:58:00 GMT 2007


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

From: Daniel Jacobowitz <drow@false.org>
To: gregoire.banderet@ge.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2248: Threads terminated by SIGTRAP in gdbserver (powerpc)
Date: Sun, 8 Apr 2007 17:56:48 -0400

 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.
 
 -- 
 Daniel Jacobowitz
 CodeSourcery



More information about the Gdb-prs mailing list