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/27898] [gdb] Cannot not find DIE
Date: Tue, 25 May 2021 14:57:07 +0000 [thread overview]
Message-ID: <bug-27898-4717-d6IFahd3FJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27898-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27898
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> Doesn't fail at gdb 9.2.
Bisects to:
...
f9b5d5ea18a3878ca48c1b747e35d456133858bc is the first bad commit
commit f9b5d5ea18a3878ca48c1b747e35d456133858bc
Author: Tom de Vries <tdevries@suse.de>
Date: Wed Jun 3 23:50:16 2020 +0200
[gdb/symtab] Fix missing breakpoint location for inlined function
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-25 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 19:11 [Bug symtab/27898] New: " vries at gcc dot gnu.org
2021-05-23 8:23 ` [Bug symtab/27898] " vries at gcc dot gnu.org
2021-05-23 15:08 ` vries at gcc dot gnu.org
2021-05-25 7:55 ` vries at gcc dot gnu.org
2021-05-25 13:04 ` vries at gcc dot gnu.org
2021-05-25 14:25 ` simark at simark dot ca
2021-05-25 14:57 ` vries at gcc dot gnu.org [this message]
2021-05-25 21:25 ` vries at gcc dot gnu.org
2021-05-25 21:26 ` vries at gcc dot gnu.org
2021-05-25 21:28 ` vries at gcc dot gnu.org
2021-05-26 9:23 ` vries at gcc dot gnu.org
2021-05-26 21:54 ` vries at gcc dot gnu.org
2021-05-27 13:22 ` cvs-commit at gcc dot gnu.org
2021-05-27 13:25 ` vries at gcc dot gnu.org
2021-05-27 13:47 ` 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-27898-4717-d6IFahd3FJ@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).