From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: jjohnstn@redhat.com
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com, mec.gnu@mindspring.com
Subject: Re: [RFA]: Fix jmain.exp to xfail for break at main
Date: Thu, 08 Jul 2004 19:01:00 -0000 [thread overview]
Message-ID: <20040708190131.B15944B104@berman.michael-chastain.com> (raw)
> See attached patch. Ok to commit?
It makes me happy. Recommended for approval.
It's up to Andrew to approve or not.
Michael C
===
Index: gdb.java/jmain.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.java/jmain.exp,v
retrieving revision 1.1
diff -u -p -r1.1 jmain.exp
--- gdb.java/jmain.exp 27 Jun 2004 00:41:39 -0000 1.1
+++ gdb.java/jmain.exp 8 Jul 2004 18:16:45 -0000
@@ -48,7 +48,7 @@ gdb_test "set print sevenbit-strings" ".
# Where the breakpoint should always land
-set bpmain "Breakpoint .* file .*jmain.java, line 6\."
+set bpmain "Breakpoint .* file .*jmain.java, line 5\."
gdb_load "${binfile}"
setup_kfail *-*-* java/1567
@@ -63,4 +63,5 @@ gdb_test "break jmain.main" "${bpmain}"
# Check that a fully qualified "main" works.
gdb_load "${binfile}"
+setup_xfail *-*-* gcc/16439
gdb_test "break \'${testfile}.main(java.lang.String\[\])\'" "${bpmain}"
--------------000805000701000707020104--
next reply other threads:[~2004-07-08 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 19:01 Michael Elizabeth Chastain [this message]
2004-07-08 19:41 ` Andrew Cagney
2004-07-08 21:01 ` Jeff Johnston
-- strict thread matches above, loose matches on Subject: below --
2004-07-08 3:42 Michael Elizabeth Chastain
2004-07-08 15:34 ` Jeff Johnston
2004-07-08 18:20 ` Jeff Johnston
2004-07-16 21:09 ` Andrew Cagney
2004-07-07 20:23 Jeff 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=20040708190131.B15944B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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