This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
gdb/2248: Threads terminated by SIGTRAP in gdbserver (powerpc)
- From: gregoire dot banderet at ge dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 4 Apr 2007 15:25:05 -0000
- Subject: gdb/2248: Threads terminated by SIGTRAP in gdbserver (powerpc)
- Reply-to: gregoire dot banderet at ge dot com
>Number: 2248
>Category: gdb
>Synopsis: Threads terminated by SIGTRAP in gdbserver (powerpc)
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Apr 04 16:28:01 BST 2007
>Closed-Date:
>Last-Modified:
>Originator: gregoire.banderet@ge.com
>Release: unknown-1.0
>Organization:
>Environment:
Host: Debian Etch, 2.6.18
Target: PowerPC MPC8349, 2.6.20
>Description:
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
Notice that I am able to do multi-thread debug on my host locally (without gdbserver).
>How-To-Repeat:
Any litlle app with a pthread_create() call will do it!
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: