public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/109411] New: missing debug information with statement frontiers Date: Tue, 04 Apr 2023 16:11:31 +0000 [thread overview] Message-ID: <bug-109411-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109411 Bug ID: 109411 Summary: missing debug information with statement frontiers Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: mpolacek at gcc dot gnu.org Target Milestone: --- $ cat main.cc #include "test.h" void invokeInline (Message & msg, int param) { someInlineFunction (msg, param); } int main () { Message msg; invokeInline (msg, 42); } $ cat test.h struct Message { int member{35}; }; template<typename T> void someInlineFunction (T & msg, int value) { msg.member += value; } $ g++ -Og -g main.cc $ gdb --nh --batch -ex 'break test.h:9' -ex run ./a.out No line 9 in file "test.h". [...] but: $ g++ -Og -g main.cc -gno-statement-frontiers $ gdb --nh --batch -ex 'break test.h:9' -ex run ./a.out Breakpoint 1 at 0x40113b: file /home/mpolacek/x/trunk/gcc/r/test.h, line 9. [...]
next reply other threads:[~2023-04-04 16:11 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-04 16:11 mpolacek at gcc dot gnu.org [this message] 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
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@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).