Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Remove XPASS on s390*
Date: Wed, 17 Mar 2004 19:18:00 -0000	[thread overview]
Message-ID: <200403171918.UAA09557@faui1d.informatik.uni-erlangen.de> (raw)

Hello,

this patch removes an XPASS in the gdb.base/watchpoint.exp test case
by calling clear_xfail for s390* (as is already done for many other
targets).

Bye,
Ulrich

ChangeLog:

	* gdb.base/watchpoint.exp (test_stepping): Clear XFAIL for
	s390* targets.

Index: gdb/testsuite/gdb.base/watchpoint.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/watchpoint.exp,v
retrieving revision 1.10
diff -c -p -r1.10 watchpoint.exp
*** gdb/testsuite/gdb.base/watchpoint.exp	6 Oct 2003 19:31:43 -0000	1.10
--- gdb/testsuite/gdb.base/watchpoint.exp	17 Mar 2004 17:45:54 -0000
*************** proc test_stepping {} {
*** 395,400 ****
--- 395,401 ----
  	clear_xfail "hppa*-*-*bsd*"
  	# It works with the generic inferior function calling code too.
  	clear_xfail "mn10300*-*-*"
+ 	clear_xfail "s390*-*-*"
  	# The following architectures define CALL_DUMMY_HAS_COMPLETED.
  	clear_xfail "hppa*-*-*hpux*"
  	gdb_test "p func1 ()" "= 73" \
-- 
  Dr. Ulrich Weigand
  weigand@informatik.uni-erlangen.de


WARNING: multiple messages have this Message-ID
From: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Remove XPASS on s390*
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <200403171918.UAA09557@faui1d.informatik.uni-erlangen.de> (raw)
Message-ID: <20040319000900.jKdQh1_Q2cDHfoluNLvsorGZGrIvmKg6xPhQRkOVW2g@z> (raw)

Hello,

this patch removes an XPASS in the gdb.base/watchpoint.exp test case
by calling clear_xfail for s390* (as is already done for many other
targets).

Bye,
Ulrich

ChangeLog:

	* gdb.base/watchpoint.exp (test_stepping): Clear XFAIL for
	s390* targets.

Index: gdb/testsuite/gdb.base/watchpoint.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/watchpoint.exp,v
retrieving revision 1.10
diff -c -p -r1.10 watchpoint.exp
*** gdb/testsuite/gdb.base/watchpoint.exp	6 Oct 2003 19:31:43 -0000	1.10
--- gdb/testsuite/gdb.base/watchpoint.exp	17 Mar 2004 17:45:54 -0000
*************** proc test_stepping {} {
*** 395,400 ****
--- 395,401 ----
  	clear_xfail "hppa*-*-*bsd*"
  	# It works with the generic inferior function calling code too.
  	clear_xfail "mn10300*-*-*"
+ 	clear_xfail "s390*-*-*"
  	# The following architectures define CALL_DUMMY_HAS_COMPLETED.
  	clear_xfail "hppa*-*-*hpux*"
  	gdb_test "p func1 ()" "= 73" \
-- 
  Dr. Ulrich Weigand
  weigand@informatik.uni-erlangen.de


             reply	other threads:[~2004-03-17 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 19:18 Ulrich Weigand [this message]
2004-03-19  0:09 ` Ulrich Weigand
2004-03-22 14:41 ` [commit] Zap XPASS from watchpoints.exp; Was: " Andrew Cagney
2004-03-22 19:08   ` [commit] Zap XPASS from watchpoints.exp; Was: [PATCH] Remove XPASS Ulrich Weigand
2004-03-22 19:22     ` Andrew Cagney
2004-03-22 19:39       ` [commit] Zap XPASS from watchpoints.exp; Was: [PATCH] Remove Ulrich Weigand

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=200403171918.UAA09557@faui1d.informatik.uni-erlangen.de \
    --to=weigand@i1.informatik.uni-erlangen.de \
    --cc=gdb-patches@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