From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/31504] debugedit writes out ELF file even when nothing has been updated
Date: Fri, 22 Mar 2024 23:47:07 +0000 [thread overview]
Message-ID: <bug-31504-13298-XCL2HliKM5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31504-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31504
--- Comment #8 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Allan McRae from comment #7)
> > What I don't fully understand is why you are expecting debugedit to NOT change
> > the debug path strings when you are asking it to. Is this because there file
> > don't actually contain any .debug sections?
>
> I don't expect that. I expect debugedit/libelf to not truncate the extra
> data that is tagged on to the ELF file.
I am sorry, but it will if it needs to change the ELF data because it has no
way of knowing what to do with this "extra data" since it isn't described in
the ELF header, program or section tables. So when the debug path strings
change and the section data becomes bigger or smaller things will move around.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-03-22 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 14:46 [Bug debugedit/31504] New: " mark at klomp dot org
2024-03-18 8:20 ` [Bug debugedit/31504] " sam at gentoo dot org
2024-03-18 22:40 ` mark at klomp dot org
2024-03-21 0:05 ` allan at archlinux dot org
2024-03-21 11:46 ` mark at klomp dot org
2024-03-21 12:07 ` mark at klomp dot org
2024-03-21 21:23 ` allan at archlinux dot org
2024-03-22 12:29 ` mark at klomp dot org
2024-03-22 22:13 ` allan at archlinux dot org
2024-03-22 23:47 ` 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-31504-13298-XCL2HliKM5@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@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).