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: Mon, 22 Sep 2003 19:22:00 -0000 [thread overview]
Message-ID: <yf23ceo7hm8.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <3F6F48A4.5040508@redhat.com> (Andrew Cagney's message of "Mon, 22 Sep 2003 15:08:20 -0400")
On Mon, 22 Sep 2003 15:08:20 -0400, Andrew Cagney <ac131313@redhat.com> said:
>> Anyways, that's what I meant. As to what the NEWS file should say,
>> well... I'm not sure that referring to Bug 1322 is actually useful,
>> because it only had that particular manifestation for a couple of
>> months, and in particular no release of GDB had that bug. You could
>> make my original statement a little more specific by saying "A
>> long-standing bug causing GDB to seg fault when loading a dynamic
>> library while debugging a Java program has been fixed." That doesn't
>> read too well, though.
> Ok, I'll drop it then (easier).
Drop the mention of Bug 1322, or drop the whole thing? I think it's
worth mentioning something about the situation: my understanding from
Tom Tromey is that it used to be almost impossible to use GDB to debug
Java, but now it's sometimes possible, which is a change worth
noting. Your call, though.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-09-22 19:22 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
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 [this message]
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=yf23ceo7hm8.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