public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/26095] New: gdb bug worked around in gcc/bb-reorder.c:pass_partition_blocks::gate
Date: Tue, 09 Jun 2020 09:14:44 +0000 [thread overview]
Message-ID: <bug-26095-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26095
Bug ID: 26095
Summary: gdb bug worked around in
gcc/bb-reorder.c:pass_partition_blocks::gate
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Current GCC contains this workaround in bb-reorder.c:
...
/* Workaround a bug in GDB where read_partial_die doesn't cope
with DIEs with DW_AT_ranges, see PR81115. */
&& !(in_lto_p && MAIN_NAME_P (DECL_NAME (fun->decl))));
...
The PR81115 is a typo, it actually refers to gcc PR 81155, as we can see from
the log message:
...
commit 8f72ce2cec8b8961f381995eb6e2c5de1cd0f3d3
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Jan 12 19:20:49 2018 +0100
re PR debug/81155 (Debug make check regressions in GCC 8.0)
PR debug/81155
* bb-reorder.c (pass_partition_blocks::gate): In lto don't
partition
main to workaround a bug in GDB.
From-SVN: r256592
...
The gcc PR (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81155 ) discusses a
GDB bug, but unfortunately it seems no GDB counterpart was filed to track it to
completion.
So, I'm filing this PR for the specific purpose of acting as GDB counterpart
for the GCC PR.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-09 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 9:14 vries at gcc dot gnu.org [this message]
2020-06-09 9:17 ` [Bug symtab/26095] " vries at gcc dot gnu.org
2020-06-09 9:32 ` vries at gcc dot gnu.org
2021-08-02 21:56 ` pinskia at gcc dot gnu.org
2023-04-24 21:21 ` pinskia 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-26095-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).