[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[avr-gcc-list] objdump disassembly lacking RAM symbol names

From: Paul \"LeoNerd\" Evans
Subject: [avr-gcc-list] objdump disassembly lacking RAM symbol names
Date: Mon, 23 May 2016 15:33:31 +0100

(First off, this is a binutils question, not really gcc itself; hoping
this is still the appropriate mailing list - if not let me know where
it should go instead).

I find that `objdump -d` doesn't give me RAM symbol names when
disassembling `ld` or `st` instructions. For example, in a program

  static uint8_t long_buttons;

My nm -d output contains:

  $ avr-nm .build/ppqbase.elf | grep long_b
  008002ec b long_buttons

So it lives at address 0x2EC in RAM, but yet

  $ avr-objdump -d .build/ppqbase.elf | grep long_b

  $ avr-objdump -d .build/ppqbase.elf | grep 2EC
     c28:       80 91 ec 02     lds     r24, 0x02EC
     c38:       80 91 ec 02     lds     r24, 0x02EC
     d00:       d0 93 ec 02     sts     0x02EC, r29

I had been hoping the output to decode these addresses into symbolic
variable names.

Is there something special I need to do to enable this?

Paul "LeoNerd" Evans

http://www.leonerd.org.uk/  |  https://metacpan.org/author/PEVANS

Attachment: pgpeWPc3PZEDO.pgp
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]