[llvm-dev] llvm-objdump: failed to parse debug information

Robinson, Paul via llvm-dev llvm-dev at lists.llvm.org
Tue Apr 28 10:50:45 PDT 2020

Agreed.  However, these don’t look like reasons for llvm-objdump to choke.

From: David Blaikie <dblaikie at gmail.com>
Sent: Tuesday, April 28, 2020 12:35 PM
To: Jerome Forissier <jerome at forissier.org>
Cc: Adrian Prantl <aprantl at apple.com>; llvm-dev at lists.llvm.org; Jordan Rupprecht <rupprecht at google.com>; Robinson, Paul <paul.robinson at sony.com>; James Henderson <jh7370.2008 at my.bristol.ac.uk>
Subject: Re: [llvm-dev] llvm-objdump: failed to parse debug information

Hmm, those look like function's that've been optimized out & that's the expected DWARF for them - but the verify stuff was implemented by Apple folks focussing on the MachO debug info distribution model that doesn't have that quirk. Would be good to fix the verifier to not hiccup on that sort of expected linked ELFine DWARF. (Adrian, etc?)

On Tue, Apr 28, 2020 at 9:31 AM Jerome Forissier <jerome at forissier.org<mailto:jerome at forissier.org>> wrote:
On 4/28/20 6:14 PM, Adrian Prantl wrote:
>> On Apr 28, 2020, at 9:03 AM, David Blaikie <dblaikie at gmail.com<mailto:dblaikie at gmail.com>> wrote:
>> What does llvm-dwarfdump tell you?
> (particularly `--verify`)

Hmmm... Quite a few errors actually, see here:


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200428/9fc34ec2/attachment-0001.html>

More information about the llvm-dev mailing list