public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vimacs.hacks at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/29918] New: GDB cannot step or break into template functions compiled with g++ -Og
Date: Mon, 19 Dec 2022 06:27:47 +0000	[thread overview]
Message-ID: <bug-29918-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29918

            Bug ID: 29918
           Summary: GDB cannot step or break into template functions
                    compiled with g++ -Og
           Product: gdb
           Version: 12.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
          Assignee: unassigned at sourceware dot org
          Reporter: vimacs.hacks at gmail dot com
  Target Milestone: ---

This is another issue posted on
https://sourceware.org/pipermail/gdb/2022-November/050431.html

For the following C++ code, I find that GDB (both 12.1 and
gdb-13-branchpoint-5-g2a517ca94d3) cannot step or break into C++ template
function t0<int> compiled with g++ -Og (GCC version 12.2.0), while LLDB from
LLVM 14.0.6 can step into this function:

template <typename T = int>
int t0(int n)
{
     int sum = 0;
     for (int i = 0; i < n; ++i) {
         sum += i * i;
     }
     return sum;
}

int t1(int n)
{
     int sum = 0;
     for (int i = 0; i < n; ++i) {
         sum += i * i;
     }
     return sum;
}

int main()
{
     int a = t0(5);
     int b = t1(5);
     return a + b;
}

The behavior in GDB looks like this:

Breakpoint 1, main () at template_func.cc:21
21      {
(gdb) n
22           int a = t0(5);
(gdb) s
t0<int> (n=n@entry=5) at template_func.cc:2
2       int t0(int n)
(gdb) 
main () at template_func.cc:23
23           int b = t1(5);
(gdb) 

The assembly output of "g++-g -Og" and "g++ -g -O0" are both attached in the
attachment of the following comments, which can be assembled and reproduce this
issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-12-19  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  6:27 vimacs.hacks at gmail dot com [this message]
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

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@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).