public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/29918] GDB cannot step or break into template functions compiled with g++ -Og
Date: Mon, 19 Dec 2022 16:30:18 +0000 [thread overview]
Message-ID: <bug-29918-4717-BOJGhPBQvZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29918-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29918
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |tromey at sourceware dot org
Last reconfirmed| |2022-12-19
Status|UNCONFIRMED |NEW
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I was able to reproduce with the Fedora 36 system gcc.
However, the line table that is emitted is weird.
First, consider the line table for lines 12-18. This
corresponds to the function t1:
File name Line number Starting address View
Stmt
prog.cc 12 0x400576
x
prog.cc 13 0x400576 1
x
prog.cc 14 0x400576 2
x
prog.cc 14 0x400576 3
prog.cc 13 0x40057b
prog.cc 14 0x400580
prog.cc 15 0x400582
x
prog.cc 15 0x400582 1
prog.cc 15 0x400587
prog.cc 14 0x400589
x
prog.cc 14 0x40058c
x
prog.cc 17 0x400590
x
prog.cc 18 0x400590 1
prog.cc 18 0x400592
Not that many lines are represented and multiple lines in this range have the
statement marker.
Now consider the line table for lines 2-9, aka t0<>:
File name Line number Starting address View
Stmt
prog.cc 2 0x4005ae
x
prog.cc 5 0x4005ae 1
prog.cc 4 0x4005b3
prog.cc 5 0x4005b8
prog.cc 6 0x4005ba
prog.cc 6 0x4005bf
prog.cc 5 0x4005c1
x
prog.cc 5 0x4005c4
x
prog.cc 9 0x4005c8
prog.cc 9 0x4005ca
This seems weird.
Perhaps gdb can work around it, after all lldb does.
I tend to suspect one of the line table patches that went in in the 12 era,
though I haven't tried bisecting or anything.
Anyway, while I agree gdb can be better, I think there's also a compiler bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-12-19 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 6:27 [Bug c++/29918] New: " vimacs.hacks at gmail dot com
2022-12-19 6:28 ` [Bug c++/29918] " vimacs.hacks at gmail dot com
2022-12-19 6:28 ` vimacs.hacks at gmail dot com
2022-12-19 16:30 ` tromey at sourceware dot org [this message]
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-29918-4717-BOJGhPBQvZ@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).