[ECOS] GDB stops randomly

[ECOS] GDB stops randomly

[Carlos Losada]

Hi,
 
I'm debugging an ecos application on an ARM/TDMI based
custom board (v. similar to EB40) using GDB through
Eclipse/CDT, but the debugger keeps stopping at random
places where there are no breakpoints set.  There is
always a SIGINT associated with this stop.  It's not
clear what's generating this signal; maybe it's an
interrupt. Configuring SIGINT not to stop debugger
loses control of my program
 
What can be done to ensure the debugger only stops at
requested breakpoints ?
 
Thanks




 
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love 
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] GDB stops randomly

[Andrew Lunn]

On Mon, Feb 05, 2007 at 03:14:02AM -0800, Carlos Losada wrote:
> Hi,
>  
> I'm debugging an ecos application on an ARM/TDMI based
> custom board (v. similar to EB40) using GDB through
> Eclipse/CDT, but the debugger keeps stopping at random
> places where there are no breakpoints set.  There is
> always a SIGINT associated with this stop.  It's not
> clear what's generating this signal; maybe it's an
> interrupt. Configuring SIGINT not to stop debugger
> loses control of my program
>  
> What can be done to ensure the debugger only stops at
> requested breakpoints ?

It could be that your program has crashed and done something
illegal. The gdb stub has taken over control and is now letting you
debug the problem.

      Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] GDB stops randomly

[Donald Walton]

I have noticed this behavior when I use Insight. The cause was editing
the program in the area where a breakpoint had been set.  The editing
process can leave the previously set breakpoint invalid.

If you have breakpoints set when you go into your program, check them
before you run the program to verify they are still valid, i.e., on a
line of code.

Don
-- 
Don Walton
Defense Research Associates, Inc.
3915 Germany Lane, Suite 102
Beavercreek, OH 43431
(937) 431-1644  x118    (office)
(937) 427-4526          (fax)

On Mon, 2007-02-05 at 03:14 -0800, Carlos Losada wrote:
> Hi,
>  
> I'm debugging an ecos application on an ARM/TDMI based
> custom board (v. similar to EB40) using GDB through
> Eclipse/CDT, but the debugger keeps stopping at random
> places where there are no breakpoints set.  There is
> always a SIGINT associated with this stop.  It's not
> clear what's generating this signal; maybe it's an
> interrupt. Configuring SIGINT not to stop debugger
> loses control of my program
>  
> What can be done to ensure the debugger only stops at
> requested breakpoints ?
>  
> Thanks
> 
> 
> 
> 
>  
> ____________________________________________________________________________________
> We won't tell. Get more on shows you hate to love 
> (and love to hate): Yahoo! TV's Guilty Pleasures list.
> http://tv.yahoo.com/collections/265 
> 


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: GDB stops randomly

[Dave Lawrence]

I have also seen this with Insight, and annoyingly the GUI doesn't 
always indicate the presence of these breakpoints.  If you delete 
gdbtk.ini (or less drastic, edit it) the problem goes away, at least, it 
goes away for the current build of code, if you add more breakpoints, 
then the problem will come back for a future build...

Donald Walton wrote:
> I have noticed this behavior when I use Insight. The cause was editing
> the program in the area where a breakpoint had been set.  The editing
> process can leave the previously set breakpoint invalid.
> 
> If you have breakpoints set when you go into your program, check them
> before you run the program to verify they are still valid, i.e., on a
> line of code.
> 
> Don


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss