RE: [cdt-debug-dev] SIGTRAP on multithreaded remote debugging withgdbser

["Patrick Noffke" <Patrick.Noffke@xxxxxxxxxxxx>]

> -----Original Message-----
> From: cdt-debug-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx]On Behalf Of Patrick Noffke
> Sent: Monday, 18 September 2006 2:54 PM
> To: cdt-debug-dev@xxxxxxxxxxx
> Subject: {Spam?} [cdt-debug-dev] SIGTRAP on multithreaded remote
> debugging withgdbserver
> 
> 
> Hi all,
> 
> I'm trying to setup remote debugging within eclipse using 
> gdbserver on my target.  I can debug fine when there is only 
> one thread or if there are no breakpoints in a multithreaded 
> app, but if I set a breakpoint for code run by a child 
> thread, when the child thread reaches the breakpoint, the 
> application terminated with code 5 (SIGTRAP).  Also eclipse 
> only shows me one thread in the Debug perspective, when I 
> know there are in fact two threads.
> 
> I've tried on two platforms (my host and the target) and the 
> same problem occurs on both.  I'm using gdb/gdbserver 6.5, 
> and eclipse 3.2.
> 
> Any ideas what I can do to solve this?
> 
> 

Just posting again -- can anyone please give me some suggestions of what to look for?  I'm happy to dig through the CDT source code if you can point me in the right direction.  Or if there is a more appropriate list to post to, please direct me there.  Others are apparently using gdbserver with multithreaded apps, so I'm guessing it's a problem with the way I'm using gdb or with how I've built my application.

One other bit of information is when I run gdbserver from my host, I get the following output:

Process auth-daemon created; pid = 25456
Listening on port 38000
Remote debugging from host 127.0.0.1
Cannot find new threads: capability not available
Cannot find new threads: capability not available
Cannot find new threads: capability not available
Cannot find new threads: capability not available
Cannot find new threads: capability not available
Cannot find new threads: capability not available
Cannot find new threads: capability not available

Then gdb in eclipse attaches to my process and stops at main.

Thanks,
Patrick