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/30265] [gdb/symtab] info var shows incorrect file/line combination for static const class member
Date: Thu, 23 Mar 2023 10:31:34 +0000 [thread overview]
Message-ID: <bug-30265-4717-2jt74ilsHF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30265-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30265
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Bisects to:
...
6d263fe46e00afd8af3d609c1afd71d05eaf745e is the first bad commit
commit 6d263fe46e00afd8af3d609c1afd71d05eaf745e
Author: Tom Tromey <tromey@adacore.com>
Date: Thu Jan 13 09:48:18 2022 -0700
Avoid bad breakpoints with --gc-sections
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-23 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 9:24 [Bug symtab/30265] New: " vries at gcc dot gnu.org
2023-03-23 10:31 ` vries at gcc dot gnu.org [this message]
2023-03-23 10:44 ` [Bug symtab/30265] " vries at gcc dot gnu.org
2023-03-23 10:54 ` vries at gcc dot gnu.org
2023-03-23 12:04 ` vries at gcc dot gnu.org
2023-03-24 8:18 ` cvs-commit at gcc dot gnu.org
2023-03-24 8:41 ` vries at gcc dot gnu.org
2023-03-24 14:46 ` cvs-commit at gcc dot gnu.org
2023-03-24 14:46 ` 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-30265-4717-2jt74ilsHF@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).