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/30728] [gdb/symtab, cc-with-dwz] FAIL: gdb.cp/breakpoint-locs.exp: break N1::C1::baz
Date: Wed, 16 Oct 2024 15:22:06 +0000 [thread overview]
Message-ID: <bug-30728-4717-dNZylY9eYa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30728-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30728
--- Comment #21 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #16)
> I wonder if gdb-index and debug-names correctly attribute these
> symbols to the including CU. If not then we'll see the bug there as well.
Good point.
FWIW, the approach of adding DW_TAG_inlined_subroutine entries to the index
(I'm currently rebasing that series) seems to work.
With .gdb_index, we get:
...
[721] N1::C1::baz:
2 [global, function]
1 [global, other]
2 [global, other]
...
and with .debug_names:
...
[ 5] _ZN2N12C13bazEv:
<4> DW_TAG_subprogram DW_IDX_compile_unit=1 DW_IDX_die_offset=<0x31>
DW_IDX_GNU_language=33 DW_IDX_GNU_linkage_name=1
<5> DW_TAG_inlined_subroutine DW_IDX_compile_unit=1
DW_IDX_die_offset=<0xac> DW_IDX_GNU_language=33 DW_IDX_GNU_linkage_name=1
<5> DW_TAG_inlined_subroutine DW_IDX_compile_unit=2
DW_IDX_die_offset=<0x13d> DW_IDX_GNU_language=33 DW_IDX_GNU_linkage_name=1
[ 9] baz:
<6> DW_TAG_subprogram DW_IDX_compile_unit=1 DW_IDX_die_offset=<0x31>
DW_IDX_GNU_language=33 DW_IDX_parent=1
<7> DW_TAG_inlined_subroutine DW_IDX_compile_unit=1
DW_IDX_die_offset=<0xac> DW_IDX_GNU_language=33 DW_IDX_parent=1
<7> DW_TAG_inlined_subroutine DW_IDX_compile_unit=2
DW_IDX_die_offset=<0x13d> DW_IDX_GNU_language=33 DW_IDX_parent=1
...
and in both cases, doing "break N1::C1::baz" results in two breakpoint
locations.
For the .gdb_index case, the "other" might be need to be "function" instead,
but regardless it seems to work.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-10-16 15:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 15:50 [Bug symtab/30728] New: " vries at gcc dot gnu.org
2023-08-06 16:16 ` [Bug symtab/30728] " vries at gcc dot gnu.org
2023-08-06 16:31 ` vries at gcc dot gnu.org
2023-08-06 18:15 ` vries at gcc dot gnu.org
2023-08-06 22:00 ` vries at gcc dot gnu.org
2023-08-07 10:23 ` vries at gcc dot gnu.org
2023-08-07 10:44 ` vries at gcc dot gnu.org
2023-08-07 15:14 ` vries at gcc dot gnu.org
2023-08-07 16:35 ` tromey at sourceware dot org
2023-08-08 23:32 ` vries at gcc dot gnu.org
2023-08-09 15:31 ` vries at gcc dot gnu.org
2023-08-10 8:49 ` vries at gcc dot gnu.org
2023-08-25 15:56 ` vries at gcc dot gnu.org
2023-10-02 12:55 ` vries at gcc dot gnu.org
2023-11-29 15:08 ` jamborm at gcc dot gnu.org
2024-01-15 0:47 ` tromey at sourceware dot org
2024-01-15 1:34 ` tromey at sourceware dot org
2024-01-15 1:54 ` tromey at sourceware dot org
2024-02-09 19:48 ` tromey at sourceware dot org
2024-02-16 2:42 ` tromey at sourceware dot org
2024-05-06 13:57 ` vries at gcc dot gnu.org
2024-10-04 22:55 ` tromey at sourceware dot org
2024-10-16 15:22 ` vries at gcc dot gnu.org [this message]
2024-10-16 23:59 ` tromey at sourceware dot org
2024-10-19 19:10 ` tromey at sourceware dot org
2024-10-20 21:05 ` tromey at sourceware dot org
2024-10-20 21:28 ` tromey at sourceware dot 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-30728-4717-dNZylY9eYa@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).