Re: [Avr-eclipse-user] avr-gdb is very slow

[Thomas H. <th...@in...>]

  I can't say that I have much experience in debugging (AVR projects), 
but I would probably leave the delay functions unchanged and switch on 
light optimization (-o1) so that the original delays functions will 
work. With -o1 the generated assembler should still at least somewhat 
resemble the original C source code in structure so single stepping will 
work as expected.

Then, I would try to work with breakpoints as much as possible, instead 
of single stepping through everything.

On 07.08.2010 19:13, Trevor Johansen wrote:
> Ahh, dwarf-2 did the trick. Debugging is a beast in itself as for 
> single stepping having the delays as single ops instead of the loops 
> normally generated makes debugging fast but if you select continue or 
> run to cursor the hardware will run at full JTAG speed and things 
> wont initialize properly. A good example is a HD44780 LCD, 
> while initializing their are quite a few delays that are mandatory but 
> if you have 1ms+ delays in your program and try to step through or 
> over them it takes a few minuets.
>
> What do you guys do to deal with delays during debug?
>
>
> On Sat, Aug 7, 2010 at 3:07 AM, Thomas Holland <th...@in... 
> <mailto:th...@in...>> wrote:
>
>      On 07.08.2010 00:19, Trevor Johansen wrote:
>     >
>     > I cannot debug in Studio, I load the /debug/project.elf but studio
>     > reports:
>     > Coordinator: Error loading object file
>     >
>     > Do I need to change the debug info format or anything in the
>     projects
>     > properties for it to work with studio?
>
>     Debug Info Format must be "dwarf-2", other than that no special
>     settings
>     are required.
>