From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ac131313@redhat.com, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files
Date: Wed, 21 Jan 2004 04:42:00 -0000 [thread overview]
Message-ID: <20040121044245.A9C6A4B359@berman.michael-chastain.com> (raw)
> BTW, Michael, any thoughts on how to fail this on systems that can't
> efficiently dump a 3g core file? Skip the test I guess, but with which
> mechanism? untested?
Unconditional UNTESTED is simple and good. "Hey, what happened with
the 3 gigabyte core dump test?" "Oh, it says UNTESTED". It's pretty
clear to me what that means.
As for *how* to do it, that is harder.
The real issue is that the criterion is not really "what is the target
triple", but "what are the resources of the specific test bed". Like,
Daniel J says that it would be awkward to enable it in the Debian
version. And it's useless for me on HP Test Drive, because I run into a
ulimit at 1 gigabyte. That's a property of HP-TD policy, not of the
hppa2.0w-hp-hpux11.11 target. I dunno how to encode that kind of
criterion in the test suite.
Michael C
next reply other threads:[~2004-01-21 4:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 4:42 Michael Elizabeth Chastain [this message]
2004-01-21 5:23 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 8:18 Michael Elizabeth Chastain
2004-01-14 14:56 Michael Elizabeth Chastain
2004-01-14 15:07 ` Andrew Cagney
2004-01-14 15:16 ` Daniel Jacobowitz
2004-01-14 15:38 ` Andrew Cagney
2004-01-14 15:44 ` Daniel Jacobowitz
2004-01-15 19:09 ` Andrew Cagney
2004-01-15 19:13 ` Daniel Jacobowitz
2004-01-20 22:02 ` Andrew Cagney
2004-01-14 3:11 Michael Elizabeth Chastain
2004-01-14 14:48 ` Andrew Cagney
2004-01-14 2:40 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=20040121044245.A9C6A4B359@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=ac131313@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