From: David Carlton <carlton@kealia.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
ezannoni@redhat.com, gdb@sources.redhat.com
Subject: Re: 6.0 NEWS; tls tests on gdb-6?
Date: Wed, 17 Sep 2003 15:53:00 -0000 [thread overview]
Message-ID: <yf2k787fm2k.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <3F6881B0.4090805@redhat.com> (Andrew Cagney's message of "Wed, 17 Sep 2003 11:45:52 -0400")
On Wed, 17 Sep 2003 11:45:52 -0400, Andrew Cagney <ac131313@redhat.com> said:
>> I wouldn't advertise the C++ stuff: what's in 6.0 won't make a
>> difference to users. It's not really going to make a difference
>> until nested type support gets fully implemented, and that isn't
>> even in the mainline yet, let alone 6.0.
> Is it more robust?
I don't recall changes that would make it much more robust, and a
quick scan of GNATS didn't remind me of any big changes. There have
been some small bug fixes, but no more than in other areas of GDB's
code.
Actually, the main robustness side effect of my C++ work has probably
been the Java support; it might be worth saying something like
A long-standing bug involving Java and dynamic libraries has been
fixed. Support for Java debugging remains minimal, however.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-09-17 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 23:58 Michael Elizabeth Chastain
2003-09-12 1:13 ` 6.0 NEWS; " Andrew Cagney
2003-09-17 15:36 ` David Carlton
2003-09-17 15:45 ` Andrew Cagney
2003-09-17 15:53 ` David Carlton [this message]
2003-09-20 20:12 ` Andrew Cagney
2003-09-22 16:10 ` David Carlton
2003-09-22 19:08 ` Andrew Cagney
2003-09-22 19:22 ` David Carlton
2003-09-22 20:04 ` Andrew Cagney
2003-09-22 20:10 ` David Carlton
2003-09-20 20:49 Michael Elizabeth Chastain
2003-09-22 20:49 Michael Elizabeth Chastain
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=yf2k787fm2k.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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