From: Nick Roberts <nickrob@snap.net.nz>
To: "Dima Sorkin" <dima.sorkin@gmail.com>
Cc: gdb@sourceware.org
Subject: gdb does not stops inside a template function
Date: Tue, 20 Jun 2006 12:21:00 -0000 [thread overview]
Message-ID: <17559.50335.118877.462855@kahikatea.snap.net.nz> (raw)
In-Reply-To: <e40293600606200138j7d719a7dq45fe0c9fc229b182@mail.gmail.com>
> Hi.
> I have the following problem with gdb6.3 :
> If I put a breakpoint on a line inside a function template,
> the gdb not always stops there.
> Please see attached ".cpp" file and the gdb session transcript
> (file: "templ_dbg.1.output").
> It can be seen that gdb stops on first call to "f",
> but not on second.
...
(gdb) break templ_dbg.cpp:4
I think you need to do:
(gdb) b int const f<int>(int const&)
(gdb) b double const f<double>(double const&)
if you want it to stop at both places. Completion makes them easier
to type:
(gdb) b int<TAB>
(gdb) b double<TAB>
(Although I can only see how to select a candidate using Emacs.)
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-06-20 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 9:50 Dima Sorkin
2006-06-20 12:21 ` Nick Roberts [this message]
2006-06-20 12:27 ` Daniel Jacobowitz
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=17559.50335.118877.462855@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dima.sorkin@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