This is the mail archive of the 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]

Re: [RFA] new test for separate debug info

OK, this is what I checked in.

2004-01-14  Elena Zannoni  <>

	* gdb.base/sepdebug.exp: Bail out of the test if we don't know
	what debug info we have. Print a better message if something goes
	wrong while producing the separate debug info file.

Index: sepdebug.exp
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/sepdebug.exp,v
retrieving revision 1.1
diff -u -p -r1.1 sepdebug.exp
--- sepdebug.exp        12 Jan 2004 17:20:41 -0000      1.1
+++ sepdebug.exp        14 Jan 2004 15:05:51 -0000
@@ -72,17 +72,22 @@ if { [test_debug_format "stabs"] } then
     # (see dejagnu/lib/framework.exp)
     unsupported "no separate debug info handling with stabs"
     return -1
+} elseif { [test_debug_format "unknown"] } then {
+    # gdb doesn't know what the debug format is. We are out of luck here.
+    unsupported "unknown debugging format"
+    return -1
 # Note: the procedure gdb_gnu_strip_debug will produce an executable called
 # ${binfile}, which is just like the executable ($binfile) but without
 # the debuginfo. Instead $binfile has a .gnudebuglink section which contains
-# the name of a idebuginfo only file. This file will be stored in the
+# the name of a debuginfo only file. This file will be stored in the
 # gdb.base/.debug subdirectory.
 if [gdb_gnu_strip_debug $binfile] {
-    unsupported "no separate debug info handling"
+    # check that you have a recent version of strip and objcopy installed
+    unsupported "cannot produce separate debug info files"
     return -1

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