From: Freddie Chopin <freddie.chopin@gmail.com>
To: Nick Clifton <nickc@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: objdump: DWARF error: could not find variable specification at offset ...
Date: Tue, 22 Sep 2020 14:40:39 +0200 [thread overview]
Message-ID: <1a0051b84f5daed21517155037b0942bc50f076c.camel@gmail.com> (raw)
In-Reply-To: <f8af4195-bdcb-d406-d13b-d0b3ea0ee657@redhat.com>
On Tue, 2020-09-22 at 13:36 +0100, Nick Clifton wrote:
> Hi Freddie,
>
> > arm-none-eabi-objdump: DWARF error: could not find variable
> > specification at offset 2f9
>
> I think that these messages are probably another instance of this
> bug:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26520
>
> Please could you try using the latest binutils sources and see if
> that fixes the problem.
Hmm... but that's the bug I reported after the first reply from Alan in
this thread, and I already wrote in bugzilla that after applying the
patch the problem is gone. Maybe you meant to post a link to a
different bug report?
Regards,
FCh
prev parent reply other threads:[~2020-09-22 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 18:15 Freddie Chopin
2020-08-19 1:08 ` Alan Modra
2020-09-22 12:36 ` Nick Clifton
2020-09-22 12:40 ` Freddie Chopin [this message]
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=1a0051b84f5daed21517155037b0942bc50f076c.camel@gmail.com \
--to=freddie.chopin@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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).