From: kaiduan xie <kaiduanx@yahoo.ca>
To: Serge Fukanchik <fuxx@mail.ru>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Gdb didnot step into the break point in class constructor in RH 8.0
Date: Fri, 17 Dec 2004 17:43:00 -0000 [thread overview]
Message-ID: <20041217174342.36548.qmail@web61202.mail.yahoo.com> (raw)
In-Reply-To: <41C31878.7040406@mail.ru>
Serge,
Nope. Thanks.
kaiduan
--- Serge Fukanchik <fuxx@mail.ru> wrote:
> Have you tried to explicitly put breakpoint at your
> constructor
> instead of just single-stepping into it?
>
> b 'TranMessage::TranMessage(int age)'
>
> This helps sometimes... :-(
>
> kaiduan xie wrote:
>
> > Many thanks for your help. But with this method,
> the
> > gdb still did not step into the constructor.
> ---
> Serge
>
>
>
______________________________________________________________________
Post your free ad now! http://personals.yahoo.ca
next prev parent reply other threads:[~2004-12-17 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 8:00 kaiduan xie
2004-12-17 12:05 ` Serge Fukanchik
2004-12-17 17:26 ` kaiduan xie
2004-12-17 17:31 ` Serge Fukanchik
2004-12-17 17:43 ` kaiduan xie [this message]
2004-12-17 19:59 Ramadass, Ramanathan
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=20041217174342.36548.qmail@web61202.mail.yahoo.com \
--to=kaiduanx@yahoo.ca \
--cc=fuxx@mail.ru \
--cc=gcc-help@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: 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).