This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] new test for separate debug info
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: ezannoni at redhat dot com
- Cc: drow at mvista dot com, gdb-patches at sources dot redhat dot com
- Date: Tue, 13 Jan 2004 21:46:56 -0500 (EST)
- Subject: Re: [RFA] new test for separate debug info
> My idea was more to incrementally add broken cases to the skip list as
> we find them.
It's not my favorite, but it's okay with me.
+} 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
I tested this. It works for me:
...
Compiled with unknown debugging format.
Does not include preprocessor macro info.
(gdb) UNSUPPORTED: gdb.base/sepdebug.exp: unknown debugging format
testcase /house/chastain/gdb/s1/gdb/testsuite/gdb.base/sepdebug.exp completed in 1 seconds
if [gdb_gnu_strip_debug $binfile] {
- unsupported "no separate debug info handling"
+ unsupported "cannot produce separate debug info files (check that you have
a recent version of strip and objcopy installed)"
return -1
}
I would rather that the message be shorter so that it does not blow up
my tables if it appears in a table. How about:
if [gdb_gnu_strip_debug $binfile] {
# check that you have a recent version of strip and objcopy
unsupported "cannot produce separate debug info files"
}
Michael C