From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
Mark Wielaard <mark@klomp.org>, Neal Gompa <ngompa13@gmail.com>
Cc: OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rpm: update to 4.14.0
Date: Thu, 9 Nov 2017 18:49:34 +0200 [thread overview]
Message-ID: <11998e65-4aa2-e2a4-7933-7058a9c84576@linux.intel.com> (raw)
In-Reply-To: <26ddd9fc-7d5d-0dd7-fc48-c7e3ca5d4128@windriver.com>
On 11/08/2017 05:31 PM, Mark Hatle wrote:
>> BTW. If you really don't want to use debugedit then you could use
>> something simple like a quick hack to list all sources I wrote some
>> time ago:
>> https://lists.fedorahosted.org/archives/list/elfutils-devel@lists.fedor
>> ahosted.org/message/VZP4G5N2ELYZEDAB3QYLXYHDGX4WMCUF/
>> (see the dwarfsrcfiles.c attachement)
>
> This may very well do what we need. Our output does not depend on RPM (or any
> specific package manager.) We had simply been using the debugedit from RPM as
> it was the best tool for the job. Now that GCC has the debug-prefix-map option,
> we no longer really need debugedit.
After poking some more at elfutils/binutils, I think that indeed the
dwarfsrcfiles.c is what we need.
The standard utilities can dump the full debug table content on you, but
they don't have a simple 'give me all sources' feature. And parsing that
output is more fragile than I thought: there are 'compile units' and
there are sources used to form them, and linking the two into a simple
list of sources isn't easy.
Thanks a lot!
Alex
next prev parent reply other threads:[~2017-11-09 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 12:14 [PATCH] rpm: update to 4.14.0 Alexander Kanavin
2017-11-03 10:14 ` Alexander Kanavin
2017-11-03 16:21 ` Khem Raj
2017-11-03 17:58 ` Mark Hatle
2017-11-06 16:00 ` Alexander Kanavin
2017-11-06 16:54 ` Mark Hatle
2017-11-07 14:53 ` Alexander Kanavin
2017-11-07 15:50 ` Otavio Salvador
2017-11-07 16:41 ` Mark Hatle
2017-11-07 21:17 ` Neal Gompa
2017-11-08 13:14 ` Alexander Kanavin
[not found] ` <1510153768.10879.80.camel@klomp.org>
2017-11-08 15:31 ` Mark Hatle
2017-11-09 13:19 ` Alexander Kanavin
2017-11-09 16:49 ` Alexander Kanavin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-18 16:00 Alexander Kanavin
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=11998e65-4aa2-e2a4-7933-7058a9c84576@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=mark.hatle@windriver.com \
--cc=mark@klomp.org \
--cc=ngompa13@gmail.com \
--cc=openembedded-core@lists.openembedded.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