All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: [PATCH] rpm: update to 4.14.0
Date: Tue, 7 Nov 2017 10:41:09 -0600	[thread overview]
Message-ID: <bdc9fa2c-70b0-f43a-f3b2-e86f6e6039b1@windriver.com> (raw)
In-Reply-To: <bfd7b5d5-328b-c0d9-0b61-75e60237b149@linux.intel.com>

On 11/7/17 8:53 AM, Alexander Kanavin wrote:
> On 11/06/2017 06:54 PM, Mark Hatle wrote:
>> You would need to interpret the dwarf symbols and find all of the referenced
>> files.  I can certainly be done with the libelf (libdwarf?), but I don't know if
>> it can be done with binutils or elfutils directly.  They may not have the
>> necessary translation to be able to assembly the pieces.
>>
>> (A lot of the filenames are listed related to a directory.. and the entries are
>> stored in different places and have to be assembled to get a similar output to
>> what debugedit gave us.)
>>
>> Writing a small standalone tool to give us this information may be very useful
>> to us though -- and would let us break the 'rpm' dependency for deb/ipkg
>> builds.. (probably)
> 
> 'readelf -wL <binary>' looks promising. I think we can simply process 
> its output from package.class (yes, a bit brittle, but easier than 
> writing a separate tool).

Yes, it looks like this has everything needed to identify the matching sources.

It will definitely have to be processed a bit, but it's all there.  (Only
concern is the processing may take significantly longer then debugedit used to..
but we won't know until we try.)

--Mark

> Alex
> 



  parent reply	other threads:[~2017-11-07 16:41 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 [this message]
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
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=bdc9fa2c-70b0-f43a-f3b2-e86f6e6039b1@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.