This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: Gdb didnot step into the break point in class constructor in RH 8.0
- From: "Ramadass, Ramanathan" <Ramanathan dot Ramadass at spirentcom dot com>
- To: "kaiduan xie" <kaiduanx at yahoo dot ca>,"Serge Fukanchik" <fuxx at mail dot ru>
- Cc: <gcc-help at gcc dot gnu dot org>
- Date: Fri, 17 Dec 2004 11:59:22 -0800
- Subject: RE: Gdb didnot step into the break point in class constructor in RH 8.0
I think this is your problem;
According to http://www.gnu.org/software/gdb/download/ANNOUNCEMENT
"When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
2 or 3 different versions of the object code. These versions have
unique mangled names (they have to, in order for linking to work), but
they have identical source code names, which leads to a great deal of
confusion. Specifically, if you set a breakpoint in a constructor or a
destructor, gdb will put a breakpoint in one of the versions, but your
program may execute the other version. This makes it impossible to set
breakpoints reliably in constructors or destructors."
Ram
-----Original Message-----
From: kaiduan xie [mailto:kaiduanx@yahoo.ca]
Sent: Friday, December 17, 2004 9:44 AM
To: Serge Fukanchik
Cc: gcc-help@gcc.gnu.org
Subject: Re: Gdb didnot step into the break point in class constructor
in RH 8.0
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