Re: problems with debugging, wrong output in assembler window from ddd

> Gesendet: Dienstag, 25. Juni 2013 um 15:28 Uhr
> Von: "Klaus Rudolph" <[email protected]>
> An: [email protected]
> Betreff: [avr-gcc-list] problems with debugging, wrong output in assembler window from ddd
>
> Hi all,
> 
> I use ddd/avr-gdb to debug in connection with simulavr.
> 
> Everythings seems to be ok, but I run into trouble if I try to debug in the assembler window:
> 
> If I set $pc=0 the assembler window output is ok.
>  0x00000000 <+0>:     rjmp    .+24            ;  0x1a <__trampolines_start>
>  0x00000002 <+2>:     rjmp    .+38            ;  0x2a <__bad_interrupt>
>  0x00000004 <+4>:     rjmp    .+36            ;  0x2a <__bad_interrupt>
> 
> 
> if I set pc to the first jump address (0x1a)
> 
> set $pc=0x1a
> the output is as follows:
>   0x0080001a:  std     Y+50, r10       ; 0x32
>   0x0080001c:  muls    r21, r31
>   0x0080001e:  std     Y+50, r10       ; 0x32
>   0x00800020:  nop
> 
> Why I got an address in ram space?
> 
> ddd 3.3.12, gdb and gcc in a lot of variants without different behaviour.
> 
> Any hints?
> 
> Regards
>  Klaus
> 
> _______________________________________________
> AVR-GCC-list mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
>