Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: [ob] Remove a dejagnu ERROR from auxv.exp
Date: Thu, 22 Jun 2006 19:35:00 -0000	[thread overview]
Message-ID: <20060622193507.GA19794@nevyn.them.org> (raw)

If your target does not support gcore at all, then it will currently
generate an ERROR running auxv.exp.  This turns it into an UNSUPPORTED,
as was probably intended.

We have some nightly build machinery here at CodeSourcery which can
automatically run DejaGNU testsuites.  It normally shows us nice pleasant
deltas between runs, but it's set to always include ERRORs, since they're
supposed to indicate a problem in the testsuite rather than in the tool
being tested.

Tested on x86_64-pc-linux-gnu and committed.

-- 
Daniel Jacobowitz
CodeSourcery

2006-06-22  Daniel Jacobowitz  <dan@codesourcery.com>

	* auxv.exp: Intercept undefined command messages before
	gdb_test_multiple does.

Index: gdb-20060226/gdb/testsuite/gdb.base/auxv.exp
===================================================================
--- gdb-20060226.orig/gdb/testsuite/gdb.base/auxv.exp	2006-06-13 21:06:57.000000000 -0700
+++ gdb-20060226/gdb/testsuite/gdb.base/auxv.exp	2006-06-13 21:07:09.000000000 -0700
@@ -139,6 +139,9 @@ gdb_test_multiple "gcore $gcorefile" "gc
     -re "Can't create a corefile\[\r\n\]+$gdb_prompt $" {
 	unsupported "gcore"
     }
+    -re "Undefined command: .*\[\r\n\]+$gdb_prompt $" {
+	unsupported "gcore"
+    }
 }
 
 # Let the program continue and die.


             reply	other threads:[~2006-06-22 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 19:35 Daniel Jacobowitz [this message]
2006-06-22 20:46 ` Mark Kettenis

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=20060622193507.GA19794@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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