From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: gdb + gcc/g++ 3.x
Date: Mon, 08 Oct 2001 13:40:00 -0000 [thread overview]
Message-ID: <20011008164135.A20141@redhat.com> (raw)
In-Reply-To: <20011008135114.A6657@nevyn.them.org>
On Mon, Oct 08, 2001 at 01:51:14PM -0400, Daniel Jacobowitz wrote:
>On Mon, Oct 08, 2001 at 01:45:58PM -0400, rwilcher wrote:
>>
>> When will you be able to use gdb with G++ 3.x? Anyone know when
>> the line number/breakpoint setting will work? is there a patch?
>
>The work hasn't been done yet, so there is no expected time. I've been
>looking in to some of the problems; I'm sure other people have as well.
What are the problems? I use gdb with g++ 3.x output all of the time
with no problems.
There are problems with optimised code but you have to sort of expect
that.
I know that there are some outstanding problems with libstdc++v3 and
gdb but they don't, AFAIK, affect setting breakpoints on lines.
cgf
next prev parent reply other threads:[~2001-10-08 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 10:48 rwilcher
2001-10-08 10:51 ` Daniel Jacobowitz
2001-10-08 13:40 ` Christopher Faylor [this message]
2001-10-08 14:15 ` Daniel Jacobowitz
2001-10-17 11:59 Scott Johnston
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=20011008164135.A20141@redhat.com \
--to=cgf@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