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] Eliminate another gdb_suppress_entire_file
Date: Thu, 22 Jun 2006 19:58:00 -0000	[thread overview]
Message-ID: <20060622195839.GA20890@nevyn.them.org> (raw)

There's a few versions of GCC 4.1 which can't compile gdb.base/store.c. It
was eventually fixed on the release branch, but I happen to be testing a
version where it's broken.  I've been making this change globally as the
function in question pops up to bite me.

Tested, committed.

-- 
Daniel Jacobowitz
CodeSourcery

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

	* gdb.base/store.exp: Don't use gdb_suppress_entire_file.

Index: gdb-20060226/gdb/testsuite/gdb.base/store.exp
===================================================================
--- gdb-20060226.orig/gdb/testsuite/gdb.base/store.exp	2004-08-04 07:59:56.000000000 -0700
+++ gdb-20060226/gdb/testsuite/gdb.base/store.exp	2006-06-13 20:57:13.000000000 -0700
@@ -30,7 +30,8 @@ set testfile "store"
 set srcfile ${testfile}.c
 set binfile ${objdir}/${subdir}/${testfile}
 if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
-    gdb_suppress_entire_file "Testcase compile failed, so all tests in this file will automatically fail."
+    untested store.exp
+    return -1
 }
 
 if [get_compiler_info ${binfile}] {


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 19:58 Daniel Jacobowitz [this message]
2006-06-23  3:11 ` Joel Brobecker
2006-06-23  3:22   ` Daniel Jacobowitz
2006-06-23  3:35     ` Joel Brobecker
2006-06-23  3:40       ` Daniel Jacobowitz
2006-06-23  4:04         ` Joel Brobecker
2006-06-23 12:34           ` Daniel Jacobowitz

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=20060622195839.GA20890@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