From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/28043] Add LSDA decoding to eu-readelf
Date: Wed, 07 Jul 2021 14:34:31 +0000 [thread overview]
Message-ID: <bug-28043-10460-4Kjrf5gsbI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28043-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28043
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Note that eu-readelf already tries to decode the .gcc_exception_table when
using -e, --exception. And the .eh_frame decoding already does get the LSDA
pointer encoding from the CIE and should show the pointer for any CFI that has
one. But there is nothing that nicely ties them together.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-07-07 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 16:30 [Bug tools/28043] New: " woodard at redhat dot com
2021-07-01 16:53 ` [Bug tools/28043] " woodard at redhat dot com
2021-07-07 14:34 ` mark at klomp dot org [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=bug-28043-10460-4Kjrf5gsbI@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).