public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/109411] missing debug information with statement frontiers Date: Fri, 27 Oct 2023 09:47:00 +0000 [thread overview] Message-ID: <bug-109411-4-kd3RgZ2yVl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109411-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109411 --- Comment #2 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- AFAICT there are mentions to test.h line numbers both with and without -gstatement-frontiers, and the mentions are the same. The problem is two-fold: - there aren't any stmt markers for the lines in the template instantiation from test.h. absent stmt markers, is_stmt remains at zero throughout the function, except for its entry on line 6 - GDB appears to disregard !is_stmt locs entirely when setting breakpoints I suppose getting markers for the instantiation would fix the problem, but I don't have any insight into why they're not generated.
prev parent reply other threads:[~2023-10-27 9:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-04 16:11 [Bug debug/109411] New: " mpolacek at gcc dot gnu.org 2023-04-04 16:13 ` [Bug debug/109411] " mpolacek at gcc dot gnu.org 2023-10-27 9:47 ` aoliva at gcc dot gnu.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-109411-4-kd3RgZ2yVl@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).