From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/31480] New: debuginfod_find_debuginfo returns corrupt debuginfo file when out of memory
Date: Wed, 13 Mar 2024 20:15:20 +0000 [thread overview]
Message-ID: <bug-31480-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31480
Bug ID: 31480
Summary: debuginfod_find_debuginfo returns corrupt debuginfo
file when out of memory
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: amerey at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
This bug has been seen when gdb ran out of memory while downloading from
debuginfod. See the following PR for more information:
https://sourceware.org/bugzilla/show_bug.cgi?id=31478
It may be that libdebuginfod fails to unlink a partially downloaded file when
out-of-memory conditions are reached. Reproducing this bug might be tricky.
We'll need to experiment with running gdb/debuginfod in a low memory
environment.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-03-13 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:15 amerey at redhat dot com [this message]
2024-03-13 20:16 ` [Bug debuginfod/31480] " amerey at redhat 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-31480-10460@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).