From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary Thomas To: Nicholas_Karagas@cirilium.com Cc: insight@sourceware.cygnus.com, ecos-discuss@sourceware.cygnus.com Subject: RE: [ECOS] twothreads in PPC simulator Date: Thu, 06 Jul 2000 10:45:00 -0000 Message-id: References: X-SW-Source: 2000-07/msg00058.html Try enabling GDB stubs in your application. Currently, most targets need special support in order to provide thread-specific debugging. This can be enabled by turning on GDB stubs within the downloaded program itself. Note: we are improving most targets so that this will no longer be necessary, i.e. you'll get thread debugging without needing to include GDB stubs in your image. I don't know if this will be the case for the PPC simulator though. On 06-Jul-00 Nicholas_Karagas@cirilium.com wrote: > Not sure where to go with this one, but I thought I'd try you guys first... > > I'm trying to use eCos for PowerPC, and right now I don't have the > hardware, so I was configuring it for the PowerPC simulator. I built the > twothreads example program, and tried debugging it in Insight. My problem > is that when I interrupt the program while it is running, I cannot get > information on the threads (i.e. thread-specific breakpoints don't work, > thread list is empty, 'info threads' in console window doesn't return > anything). The same thing happens in -nw mode. I double-checked, and eCos > is configured for multithreaded debugging (I just used the default PowerPC > simulator template, and added the IP stack package). My versions are as > follows: > > gcc - 2.95.2 19991024 > gdb - 5.0 > eCos - 1.3.1 > host - i686-pc-cygwin (on NT 4.0) > target - powerpc-eabi > > Thanks for any help. > > Nicholas Karagas > Associate Software Engineer > Cirilium Corporation > Tempe, AZ > (480) 317-1144 >