From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ezannoni@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] new test for separate debug info
Date: Wed, 14 Jan 2004 02:47:00 -0000 [thread overview]
Message-ID: <20040114024656.2FD964B104@berman.michael-chastain.com> (raw)
> 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
next reply other threads:[~2004-01-14 2:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 2:47 Michael Elizabeth Chastain [this message]
2004-01-14 15:09 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 22:24 Michael Elizabeth Chastain
2004-01-13 23:37 ` Elena Zannoni
2004-01-13 5:19 Michael Elizabeth Chastain
2004-01-13 17:18 ` Elena Zannoni
2004-01-13 2:28 Michael Elizabeth Chastain
2004-01-13 4:49 ` Elena Zannoni
2003-11-14 19:37 Michael Elizabeth Chastain
2003-11-14 20:09 ` Elena Zannoni
2004-01-12 17:20 ` Elena Zannoni
2004-01-12 22:01 ` Andrew Cagney
2004-01-12 22:28 ` Daniel Jacobowitz
2004-01-12 23:11 ` Elena Zannoni
2004-01-12 23:20 ` Daniel Jacobowitz
2004-01-13 3:12 ` Ian Lance Taylor
2004-01-16 19:55 ` Andrew Cagney
2004-01-16 22:41 ` Daniel Jacobowitz
2003-11-14 15:18 Michael Elizabeth Chastain
2003-11-14 15:52 ` Elena Zannoni
2003-11-14 5:14 Michael Elizabeth Chastain
2003-11-14 14:30 ` Elena Zannoni
2003-11-14 4:57 Michael Elizabeth Chastain
2003-11-14 14:32 ` Elena Zannoni
2003-11-13 17:55 Michael Elizabeth Chastain
2003-11-13 19:23 ` Elena Zannoni
2003-11-13 20:08 ` Elena Zannoni
2003-11-13 23:15 ` Elena Zannoni
2003-11-14 4:22 ` Daniel Jacobowitz
2003-11-14 14:34 ` Elena Zannoni
2003-11-13 16:49 Michael Elizabeth Chastain
2003-11-12 22:13 Elena Zannoni
2003-11-12 22:29 ` Daniel Jacobowitz
2003-11-13 16:18 ` Andrew Cagney
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=20040114024656.2FD964B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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