Thanks Kelly, I'm not sure of all that "volatile" does (I know I need it for variables that I use both in interrupts and out). The lines may have been executed, but it's very... not nice when 10 XOR 00 = 00 because another line has been executed without me knowing. I may turn optimization back on after I'm finished debugging, I'll see if it still works. Thanks again, Cat -------------------------------------------------- From: "David Kelly" <dkelly@hiwaay.net> Sent: Sunday, June 08, 2008 12:19 PM To: <AVR-Chat@yahoogroups.com> Subject: Re: [AVR-Chat] AvrStudio4 (2008), WinAVR (2007-05...) and Dragon problem debugging C code (jtag) > > On Jun 7, 2008, at 5:13 PM, Cat Hotmail wrote: > >> I'm having this weird problem whereby I am able to debug, and to step >> through the program, but it just ignores/skips some of the lines. > > > As you have found when -Os is changed to -O0 all your "lines" appear > as expected in the debugger. You didn't say whether "skipped" lines > were executed or not, I suspect they were. Just optimized to where the > debugger couldn't single out and associate assembly code with source > code. > > To some extent you could use more volatile modifiers to create > distinct source code line demarcations that will single step debug. > > -- > David Kelly N4HHE, dkelly@HiWAAY.net > ======================================================================== > Whom computers would destroy, they must first drive mad. > > > ------------------------------------ > > Yahoo! Groups Links > > > >
Message
Re: [AVR-Chat] AvrStudio4 (2008), WinAVR (2007-05...) and Dragon problem debugging C code (jtag)
2008-06-09 by Cat Hotmail
Attachments
- No local attachments were found for this message.