From: David Carlton <carlton@kealia.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Anthony Green <green@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [commit/java] Work around java/1565 in jmisc.exp
Date: Tue, 24 Feb 2004 17:53:00 -0000 [thread overview]
Message-ID: <yf2ishws6so.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <403B8E21.3020100@gnu.org> (Andrew Cagney's message of "Tue, 24 Feb 2004 12:47:13 -0500")
On Tue, 24 Feb 2004 12:47:13 -0500, Andrew Cagney <cagney@gnu.org> said:
>> On Tue, 24 Feb 2004 11:12:11 -0500, Andrew Cagney <cagney@gnu.org> said:
>>>> This patch modifies jmisc.exp to work around the very very long
>>>> standing bug java/1565 (just that no one thought to report it?).
>> It's bug java/1164 (with a corresponding GDB PR).
That should say "GCC PR", of course.
>> As Michael pointed out, one of the other Java tests already does
>> what you want. It would be good for this test to be KFAILed,
>> though, given that you're the second person to have proposed that
>> change in the last two or three months.
> No, "jmain.exp" does what I want - test for three potential bugs.
> The old "jmisc.exp" really isn't doing anything other than causing
> cascading failures :-(
I posted the above before I saw your jmain.exp; I agree that breaking
up the "can we break on main" functionality into a separate test is a
much better idea than the current setup.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-02-24 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 16:12 Andrew Cagney
2004-02-24 16:15 ` Daniel Jacobowitz
2004-02-24 16:42 ` Andrew Cagney
2004-02-24 16:46 ` Daniel Jacobowitz
2004-02-24 17:07 ` David Carlton
2004-02-24 17:47 ` Andrew Cagney
2004-02-24 17:49 ` Daniel Jacobowitz
2004-02-24 19:55 ` Andrew Cagney
2004-02-24 17:53 ` David Carlton [this message]
2004-02-24 16:33 Michael Elizabeth Chastain
2004-02-24 17:21 ` Andrew Cagney
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=yf2ishws6so.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=green@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