From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/26738] .debug_line reference above end of section (mipsel)
Date: Tue, 02 Mar 2021 13:20:58 +0000 [thread overview]
Message-ID: <bug-26738-11298-Evxt9xkLye@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26738-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26738
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Tentative fix:
...
diff --git a/dwz.c b/dwz.c
index af1c5af..5effbc1 100644
--- a/dwz.c
+++ b/dwz.c
@@ -15150,7 +15150,7 @@ write_multifile (DSO *dso)
debug_sections[DEBUG_MACRO].new_size)
!= (ssize_t) debug_sections[DEBUG_MACRO].new_size)
|| (strp_htab != NULL && write_multifile_strp ())
- || (line_htab != NULL && write_multifile_line ()))
+ || write_multifile_line ())
{
error (0, 0, "Error writing multi-file temporary files");
ret = 1;
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-02 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 15:56 [Bug default/26738] New: .debug_line reference above end of section doko at debian dot org
2020-10-15 15:57 ` [Bug default/26738] " doko at debian dot org
2020-10-15 16:39 ` mark at klomp dot org
2020-10-19 21:07 ` [Bug default/26738] .debug_line reference above end of section (mipsel) mark at klomp dot org
2021-03-02 13:20 ` vries at gcc dot gnu.org [this message]
2021-03-02 13:57 ` vries at gcc dot gnu.org
2021-03-04 8:18 ` vries at gcc dot gnu.org
2021-03-05 6:32 ` vries at gcc dot gnu.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-26738-11298-Evxt9xkLye@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@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).