From: Daniel Jacobowitz <drow@mvista.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
Cc: michaelstather@nuzi.de, gdb@sources.redhat.com
Subject: Re: Does current GDB work correctly woth gcc 3.3 (3.4)?
Date: Wed, 28 Jan 2004 14:51:00 -0000 [thread overview]
Message-ID: <20040128145051.GA7372@nevyn.them.org> (raw)
In-Reply-To: <48828.203.199.140.162.1075297416.squirrel@webmail.codito.com>
On Wed, Jan 28, 2004 at 07:13:36PM +0530, Ramana Radhakrishnan wrote:
> Hi,
>
> > I already asked this several times before, but I got no answer:
> > Does the upcoming gcc work correctly with gcc 3.x gereated executables
> > or does the "ignore breakpoints in constructor" bug still exist.
> >
>
> A more polite question would work . I tried out your stuff with g++
> version 3.2 as well as cvs head for today using gdb cvs head also.
> Attached are the session logs. It works for me over here.It would be
> better if you could do something like this.
>
>
>
>
> > If yes, when it´s estimated to be fixed?
>
> me thinks it is already fixed. Maybe I am using a wrong test case but one
> would not know. . A proper test case would definitely help. So maybe you
> can send a better test case and hope for a reply.
>
>
> >
> > I think all linux developers need this to work with gdb reliabely!
> All C++ developers need this to work with gdb reliably would be a better
> way of putting things.
It is half-fixed. Some constructors can be breakpointed, some (for
base classes) can not. A proper fix is still being worked on.
A whole lot of GNU/Linux and C++ developers don't seem to be crippled
by this. It's really not that hard to work around. Set a breakpoint
by PC if necessary.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2004-01-28 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 9:27 Michael Stather
2004-01-28 13:31 ` Ramana Radhakrishnan
2004-01-28 14:51 ` 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=20040128145051.GA7372@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=michaelstather@nuzi.de \
--cc=ramana.radhakrishnan@codito.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