From: Mark Wielaard <mark@klomp.org>
To: Milian Wolff <mail@milianw.de>
Cc: elfutils-devel@sourceware.org
Subject: Re: dwfl_attach_state alternative taking Ebl?
Date: Wed, 05 Apr 2017 12:46:00 -0000 [thread overview]
Message-ID: <1491396394.8380.78.camel@klomp.org> (raw)
In-Reply-To: <1563796.tLH0IFhUAp@milian-kdab2>
On Thu, 2017-03-30 at 13:14 +0200, Milian Wolff wrote:
> > OK. How do you know the Elf architecture in that case? How and by what
> > is it given? Is that an EM constant or some architecture string?
>
> In our case we either get it from perf, or the user specifies it directly on
> the command line. In both cases it is a string like "x86_64", "arm" or
> "aarch64". We map that to a list of architectures we know about, see e.g.:
>
> http://code.qt.io/cgit/qt-creator/perfparser.git/tree/app/
> perfregisterinfo.h#n29
>
> So, any API that would allow us to map these architectures directly to a dwfl/
> elf counterpart would simplify our code, or at least would make it easier to
> understand, as we wouldn't have to wait for an Elf file we can open before
> calling dwfl_attach_state.
So you map from simple architecture name like "x86" or "powerpc". But
what mechanism do you have to whether that is 32 or 64 bit, and big or
little endian?
Thanks,
Mark
next prev parent reply other threads:[~2017-04-05 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 14:50 Milian Wolff
2017-03-29 19:48 ` Mark Wielaard
2017-03-29 21:57 ` Milian Wolff
2017-03-30 10:57 ` Mark Wielaard
2017-03-30 11:14 ` Milian Wolff
2017-04-05 12:46 ` Mark Wielaard [this message]
2017-04-05 12:53 ` Ulf Hermann
2017-04-05 13:04 ` Milian Wolff
2017-04-11 12:10 ` Mark Wielaard
2017-04-11 12:28 ` Ulf Hermann
2017-04-19 19:50 ` Mark Wielaard
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=1491396394.8380.78.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=mail@milianw.de \
/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).