From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/25083] Unexpected hangs at elf32_updatefile.c:518
Date: Sat, 19 Oct 2019 19:27:00 -0000 [thread overview]
Message-ID: <bug-25083-10460-8CiHGEP26Y@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25083-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25083
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-10-19
CC| |mark at klomp dot org
Ever confirmed|0 |1
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
It doesn't really "hang", but tries to write out an enormous amount of data.
The issue is that both hangxx files have allocated section with a very large
offset:
[ 9] .rela.dyn NOBITS 00000000000015b8 d600000280 00002688 24
A
5 0 8
[26] .bss NOBITS 0000000000212b80 e8ff012b60 00000490 0
WA 0 0 64
When writing out the new file eu-unstrip will dutifully try to place those
sections at that exact offset in the file by putting "filler" (zeros) in the
file till the offset is reached. That simply takes a very long time (or till
the disk space runs out).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-10-19 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 15:00 [Bug libelf/25083] New: " leftcopy.chx at gmail dot com
2019-10-19 19:27 ` mark at klomp dot org [this message]
2019-10-20 3:43 ` [Bug libelf/25083] " leftcopy.chx at gmail dot com
2019-10-20 10:18 ` mark at klomp dot org
2019-10-20 15:24 ` mark at klomp dot org
2019-10-21 20:58 ` [Bug tools/25083] unstrip tries to write out an enormous amount of data mark at klomp dot org
2019-10-26 0:21 ` mark at klomp dot org
2020-07-28 4:46 ` meave390 at gmail dot com
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-25083-10460-8CiHGEP26Y@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).