From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/30975] elfutils incorrectly reports core files with non-contiguous segments
Date: Thu, 02 Nov 2023 13:48:50 +0000 [thread overview]
Message-ID: <bug-30975-10460-WqmyUrmDjq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30975-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-11-02
Status|UNCONFIRMED |NEW
CC| |mark at klomp dot org
Ever confirmed|0 |1
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
I believe your analysis of the code is correct. But I don't yet know
what the correct fix for this is. We'll probably need to do multiple
passes over the list to combine the segments that are part of the same
ELF file. In theory we support split Dwfl_Modules for e.g kernel modules,
which are ET_REL files where the sections are loaded individually. But
I am not yet sure how that would translate to general user space
executables/shared libraries (which are assumed to have just one base
load address). Maybe we should ignore any segment not having the executable
flag set?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-02 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 14:04 [Bug general/30975] New: " pablogsal at gmail dot com
2023-11-02 13:48 ` mark at klomp dot org [this message]
2023-11-02 13:55 ` [Bug general/30975] " pablogsal at gmail dot com
2023-11-12 20:19 ` amerey at redhat dot com
2023-11-13 16:21 ` amerey at redhat dot com
2023-11-21 18:26 ` amerey at redhat dot com
2023-11-23 14:51 ` pablogsal at gmail dot com
2023-11-23 15:10 ` amerey at redhat dot com
2023-12-21 0:49 ` mark at klomp dot org
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-30975-10460-WqmyUrmDjq@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).