[En-Nut-Discussion] "step over" and "step into" fail debugging with AVR Studio

[José Vallet]

Hello all.

I am trying to debug my code, and after a looong fight I was able to 
compile the code including NutOS debug info (although I only need to 
debug my code, this way seems to work better for the debugger).

The only way that I could include the NunOS debug info was following 
http://groups.google.com/group/osdeve_mirror_rtos_En-Nut-Discussion/browse_thread/thread/55070b4dcdd2e659/5a48b93065d895fa?lnk=st&q=I+have+successfully+compiled+and+debugged+ethernut&rnum=1#5a48b93065d895fa

Now I can see all the NutOS code in the debugger, and even better, it 
does not get stuck everywhere.

BUT

My problem now is that I _cannot_ go step by step with AVR Studio. When 
the debugger is pointing to a line of code, if I press the "step over" 
button, instead of jumping to the next line of code it jumps deep inside 
  NutOS code. Furthermore, if the debugger points to any of my functions 
and press "step into" buttons, the debugger also goes inside all the 
NutOS functions, not inside mine. As a result debugging is really 
difficult.

Before I was able to include the debug info from NutOS in my .elf, I had 
similar problems, but instead of jumping to the source code of NutOS, 
AVR Studio's debugger was jumping to the assembler code ALL the time...

Anybody with the same problem? Any idea how to solve it?

My environment

- WinXP Pro w/sp2
- Ethernut 4.0.2
- WinAVR-20060125
- AVRStudio 4.12.462  Service Pack 1
- debug format elf w/dwarf-2
- Ethernut 2.1b target
- ATMEL AVRATJTAGICE_MKII


Thanks!!
José