From: Daniel Jacobowitz <drow@mvista.com>
To: Cedric.Pillonel@swisscom.com
Cc: gdb@sources.redhat.com, gdb-prs@sources.redhat.com
Subject: Re: Breakpoints in ctor and gcc 3.x
Date: Wed, 01 Oct 2003 14:48:00 -0000 [thread overview]
Message-ID: <20031001140946.GB3720@nevyn.them.org> (raw)
In-Reply-To: <57CE6CB990693A478C1106BBC91398BA7D559D@sxmbx04.corproot.net>
On Wed, Oct 01, 2003 at 08:37:37AM +0200, Cedric.Pillonel@swisscom.com wrote:
> GCC doesn't stop on breakpoints in C++ constructors or destructors.
> I'm using gcc 3.2 and gdb 5.2.1. I know it is a known bug with gcc 3.x.
>
> This bug is old and I'm surprised that it still has not been fixed !!!
> Is there any workaround?
> When will it be fixed ? I think it is a serious one since you can't debug your ctor or dtor !
I have hopes to fix it for 6.1. But like everything else in GDB, it
gets fixed when someone has both time and motivation to do it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-10-01 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 6:38 Cedric.Pillonel
2003-10-01 6:57 ` Jim Blandy
2003-10-01 10:35 ` about class LOC_COMPUTED_ARG ankit thukral
2003-10-01 14:49 ` Daniel Jacobowitz
2003-10-02 3:52 ` Jim Blandy
2003-10-01 14:48 ` Daniel Jacobowitz [this message]
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=20031001140946.GB3720@nevyn.them.org \
--to=drow@mvista.com \
--cc=Cedric.Pillonel@swisscom.com \
--cc=gdb-prs@sources.redhat.com \
--cc=gdb@sources.redhat.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