From: Hengqi Chen <hengqi.chen@gmail.com>
To: Mark Wielaard <mark@klomp.org>, elfutils-devel@sourceware.org
Subject: Re: dwarf_nextcu can't handle abbrev offset correctly ?
Date: Fri, 2 Dec 2022 10:03:54 +0800 [thread overview]
Message-ID: <34b3893d-bbee-9ae8-649e-e0617d07bd41@gmail.com> (raw)
In-Reply-To: <3a2e39431abb0882b445269420f923e026b6c381.camel@klomp.org>
Hi Mark,
On 2022/12/1 23:54, Mark Wielaard wrote:
> Hi Hengqi,
>
> On Thu, 2022-12-01 at 23:34 +0800, Hengqi Chen via Elfutils-devel
> wrote:
>> I am using pahole (which relies on libelf) to process an elf file
>> ([0]):
>>
>> LLVM_OBJCOPY="objcopy" pahole -J --btf_gen_floats --btf_base
>> vmlinux adl_pci9111.ko
>>
>> This failed with:
>>
>> die__process: DW_TAG_compile_unit, DW_TAG_type_unit,
>> DW_TAG_partial_unit or DW_TAG_skeleton_unit expected got member
>> (0xd)!
>>
>> The .ko contains two CU, readelf says that the abbrev offsets are at
>> 0 and 0x907,
>> but dwarf_nextcu reports that abbrev offsets are both at 0.
>>
>> pahole expects to find DW_TAG_compile_unit, but seams that the wrong
>> abbrev offset causes the failure.
>>
>>
>> [0]: https://gitlab.com/chenhengqi/loong-debug
>
> I took a quick look at the adl_pci9111.ko there. And the issue is that
> elfutils doesn't know how to handle the relocations for LoongArch yet.
>
> Specifically the backend should implement the reloc_simple_type hook.
>
> Cheers,
>
> Mark
That's great. Thanks for the pointer. Will try to implement it.
Cheers,
---
Hengqi
prev parent reply other threads:[~2022-12-02 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 15:34 Hengqi Chen
2022-12-01 15:54 ` Mark Wielaard
2022-12-02 2:03 ` Hengqi Chen [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=34b3893d-bbee-9ae8-649e-e0617d07bd41@gmail.com \
--to=hengqi.chen@gmail.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).