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
