From: Andreas Schwab <schwab@suse.de>
To: "Peng Yu" <pengyu.ut@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to debug C++ functor in gdb?
Date: Sun, 29 Oct 2006 23:20:00 -0000 [thread overview]
Message-ID: <jed58ak8vb.fsf@sykes.suse.de> (raw)
In-Reply-To: <366c6f340610291301p523de441r6b691975822a9131@mail.gmail.com> (Peng Yu's message of "Sun, 29 Oct 2006 15:01:34 -0600")
"Peng Yu" <pengyu.ut@gmail.com> writes:
> I set a break point at the line indicated in the comment. Then I call
> the following command in gdb. It failed. Is there any way that I can
> call the functor _f?
>
> (gdb) p _f(10)
> Couldn't find method functor<function<int> >::_f
(gdb) p _f.'operator()'(10)
$1 = 10
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-10-29 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 21:01 Peng Yu
2006-10-29 23:20 ` Andreas Schwab [this message]
2006-11-15 0:12 ` Peng Yu
2006-11-15 1:23 ` Andreas Schwab
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=jed58ak8vb.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb@sourceware.org \
--cc=pengyu.ut@gmail.com \
/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