This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RFA: gdb.base/auxv.exp: 'untested' instead of gdb_suppress_entire_file


Looking at this message:
http://sourceware.org/ml/gdb-patches/2005-04/msg00143.html

I gather that changes like the below are welcome --- right?

2005-05-02  Jim Blandy  <jimb@redhat.com>

	* gdb.base/auxv.exp: Call 'untested' and return -1 instead of
	calling gdb_suppress_entire_file.

Index: gdb/testsuite/gdb.base/auxv.exp
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/auxv.exp,v
retrieving revision 1.1
diff -c -p -r1.1 auxv.exp
*** gdb/testsuite/gdb.base/auxv.exp	13 Apr 2004 16:39:08 -0000	1.1
--- gdb/testsuite/gdb.base/auxv.exp	2 May 2005 19:08:09 -0000
*************** set corefile ${objdir}/${subdir}/${testf
*** 37,43 ****
  set gcorefile ${objdir}/${subdir}/${testfile}.gcore
  
  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."
  }
  
  # Use a fresh directory to confine the native core dumps.
--- 37,44 ----
  set gcorefile ${objdir}/${subdir}/${testfile}.gcore
  
  if  { [gdb_compile "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable {debug}] != "" } {
!     untested "couldn't compile ${srcdir}/${subdir}/${srcfile}"
!     return -1
  }
  
  # Use a fresh directory to confine the native core dumps.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]