From: Lieven Hey <lieven.hey@kdab.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: James Clark <james.clark@arm.com>,
linux-perf-users@vger.kernel.org, acme@kernel.org
Subject: Re: [PATCH] include program header in elf files generated by perf inject
Date: Tue, 13 Sep 2022 16:34:42 +0200 [thread overview]
Message-ID: <5cc0869d-99fd-628d-b2f8-73aa9dd8f88c@kdab.com> (raw)
In-Reply-To: <YyCKbAFmZohv0ISJ@leoy-yangtze.lan>
Hi Leo,
6d518ac7be62 was not in my code base. It fixes the issue, but not in my
usecase. In my usecase I open the elf files with elfutils, but elfutils
requires a program header to be present.
Cheers,
Lieven
Am 13.09.22 um 15:49 schrieb Leo Yan:
> Hi Lieven,
>
> On Tue, Sep 13, 2022 at 03:34:18PM +0200, Lieven Hey wrote:
>> Hi,
>>
>> perf is unable to open elf files generated by perf inject.
>>
>> Example:
>> Create a file named test.dart with the following content:
>>
>> void main() {
>> print("Hello World");
>> }
>>
>> and then run
>>
>> perf record --call-graph dwarf -k 1 dart --generate-perf-jitdump test.dart
>> perf inject -j -i perf.data -o perf.data.jitted
>>
>> The problem exists since 2d86612aacb78. The commit added some code that now
>> requires an elf file to have a valid program header.
>
> Sorry I missed this patch.
>
> Could you confirm if the commit 6d518ac7be62 ("perf symbol: Fail to read
> phdr workaround") is included in your local code base?
>
> After a quick look for this patch, I think it is doing right thing.
> Just want to check if this is the same issue with the one fixed by the
> commit 6d518ac7be62. I will review it in details in my next 1~2 days.
>
>>> Can you reply-all on the original mailing list thread with this and a
>>> 'to' to Leo. It's probably best to continue the discussion there so Leo
>>> is aware.
>
> Thanks a lot, James.
>
> Leo
next prev parent reply other threads:[~2022-09-13 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 8:49 [PATCH] include program header in elf files generated by perf inject Lieven Hey
2022-08-25 13:51 ` James Clark
[not found] ` <6e0ebfb6-9fbf-073c-94b0-a799b9ec657f@kdab.com>
[not found] ` <e3c57763-eb3d-e8cc-c3b7-36a33e86ad6a@arm.com>
[not found] ` <1cc13a5d-bb41-edbb-ade7-62d4a678c0f9@kdab.com>
[not found] ` <cf2f3f27-1002-dbd0-d851-465b169c2031@arm.com>
2022-09-13 13:34 ` Lieven Hey
2022-09-13 13:49 ` Leo Yan
2022-09-13 14:34 ` Lieven Hey [this message]
2022-09-14 13:52 ` Leo Yan
2022-09-15 8:17 ` Lieven Hey
2022-09-15 8:35 ` Leo Yan
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=5cc0869d-99fd-628d-b2f8-73aa9dd8f88c@kdab.com \
--to=lieven.hey@kdab.com \
--cc=acme@kernel.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-perf-users@vger.kernel.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 NNTP newsgroup(s).