From: Brian Budge <brian.budge@gmail.com>
To: gdb@sourceware.org
Subject: Re: can't step into, or print variables inside of C++ template function
Date: Wed, 27 Apr 2011 16:43:00 -0000 [thread overview]
Message-ID: <BANLkTi=rr_BL1S=jYjMB3qhwuG988txuuA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=ePWsHgK3rQZdUMQW=OFj+t67qSw@mail.gmail.com>
A quick update: This works under gcc 4.4. Unsure if a bug should be
filed against gdb to work with newer debug information, or against gcc
for breaking the debug information.
Thanks,
Brian
On Wed, Apr 27, 2011 at 9:41 AM, Brian Budge <brian.budge@gmail.com> wrote:
> Hi all -
>
> We're using GDB to debug a C++ project, and we're running into
> something new: We can set a breakpoint in a template function (more
> precisely, a method inside a template class), but we can't list the
> source there, we can't step or next reliably from there, and we can't
> print the values of local variables there.
>
> We tried explicitly instantiating the templates in their own
> translation unit, but this didn't help with the problem. We have
> tried gdb 7.0.1 and 7.2. We're using g++ 4.5.1 under Ubuntu on
> x86-64.
>
> I should also mention we've been using gdb to debug this exact code
> for well over a year. I'm not positive, but it's possible that we
> upgraded from gcc 4.4 to 4.5 since we last debugged this specific
> piece of code.
>
> Has anyone seen this? Is there a workaround?
>
> Thanks,
> Brian
>
next prev parent reply other threads:[~2011-04-27 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 16:41 Brian Budge
2011-04-27 16:43 ` Brian Budge [this message]
2011-04-29 13:15 ` Jan Kratochvil
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='BANLkTi=rr_BL1S=jYjMB3qhwuG988txuuA@mail.gmail.com' \
--to=brian.budge@gmail.com \
--cc=gdb@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).