public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Luke Diamand <luke@diamand.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Roland McGrath <roland@hack.frob.com>, elfutils-devel@sourceware.org
Subject: Re: dwfl_link_map_report() on a core file with sysroot? Opens the wrong solibs?
Date: Sun, 06 Jan 2019 22:04:00 -0000	[thread overview]
Message-ID: <CAE5ih7_SJuCSBpuDuuL9pA8YA7hUEuHhtiH2R-eOWEKwTHBCWw@mail.gmail.com> (raw)
In-Reply-To: <20190106210435.GA13674@wildebeest.org>

On Sun, 6 Jan 2019 at 21:04, Mark Wielaard <mark@klomp.org> wrote:
>
> On Fri, Dec 14, 2018 at 01:44:17PM +0000, Luke Diamand wrote:
> > On Thu, 13 Dec 2018 at 22:37, Roland McGrath <roland@hack.frob.com> wrote:
> > >
> > > I think it's just missing. The hardest part is just deciding how the configuration should work.
> >
> > Thanks. My current attempt adds a new function call,
> > dwfl_set_sysroot(), which works, but feels a bit clunky. I might see
> > if I can just use the find_elf callback instead.
>
> If you got this working please let us know.
> It might help others and/or deciding how to add a proper
> interface/config/hook for it.
>

I have a fix which I think does the right thing - I've been playing
around with core files from a Raspberry Pi and analysing them on a
Linux x86 PC using eu-stack. Christmas and New Year intervened but I
hope to submit something once I've recovered from that.

Thanks!
Luke

      reply	other threads:[~2019-01-06 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 20:27 Luke Diamand
     [not found] ` <CAORpzuOC4yGnrbtYjD=kxhJ-ytfJ0tQ3+iDq1NPZ9g8jenVi0g@mail.gmail.com>
2018-12-14 13:44   ` Luke Diamand
2019-01-06 21:04     ` Mark Wielaard
2019-01-06 22:04       ` Luke Diamand [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=CAE5ih7_SJuCSBpuDuuL9pA8YA7hUEuHhtiH2R-eOWEKwTHBCWw@mail.gmail.com \
    --to=luke@diamand.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.org \
    --cc=roland@hack.frob.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 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).