From: Freddie Chopin <freddie.chopin@gmail.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: objdump: DWARF error: could not find variable specification at offset ...
Date: Mon, 17 Aug 2020 20:15:59 +0200 [thread overview]
Message-ID: <e64ed0f6aa25d60a158d0a2c75fd2a4c191fb223.camel@gmail.com> (raw)
Hello!
I have multiple embedded projects that - as part of the compilation
process - produce also assembly listing with command similar to this
one:
$ arm-none-eabi-objdump -S --demangle distortosTest.elf > distortosTest.lss
This worked flawlessly up to (and including) previous release of
binutils. In 2.35 something changed. The assembly listing is still
generated and it seems to be correct (I did not check it very
thoroughly), the command ends with no fatal errors (it returns "0" to
the shell), however I see multiple errors like these:
arm-none-eabi-objdump: DWARF error: could not find variable specification at offset 2f9
arm-none-eabi-objdump: DWARF error: could not find variable specification at offset 305
arm-none-eabi-objdump: DWARF error: could not find variable specification at offset 311
...
If I take the .elf file produced by the "new" toolchain (it also
includes GCC 10.2) and do the command above but with objdump from the
"old" toolchain (binutils 2.34), then there is no error. In a reversed
scenario (.elf produced by "old" toolchain, passed to "new" objdump) I
see 10x more errors like the ones above.
I have no idea what does it mean, whether its a problem or not, what
variables are a problem here and how to solve it. Any hints will be
appreciated, I probably should provide some more details, but I don't
really know where to start...
P.S. Please keep me CCed.
Regards,
FCh
next reply other threads:[~2020-08-17 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 18:15 Freddie Chopin [this message]
2020-08-19 1:08 ` Alan Modra
2020-09-22 12:36 ` Nick Clifton
2020-09-22 12:40 ` Freddie Chopin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e64ed0f6aa25d60a158d0a2c75fd2a4c191fb223.camel@gmail.com \
--to=freddie.chopin@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).