From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16488 invoked by alias); 21 Jan 2004 04:42:38 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16472 invoked from network); 21 Jan 2004 04:42:37 -0000 Received: from unknown (HELO maynard.mail.mindspring.net) (207.69.200.243) by sources.redhat.com with SMTP; 21 Jan 2004 04:42:37 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AjACK-0006nz-00; Tue, 20 Jan 2004 23:42:36 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id A9C6A4B359; Tue, 20 Jan 2004 23:42:45 -0500 (EST) To: ac131313@redhat.com, mec.gnu@mindspring.com Subject: Re: [patch/rfc/testsuite] Test GDB on not-so-little core files Cc: gdb-patches@sources.redhat.com Message-Id: <20040121044245.A9C6A4B359@berman.michael-chastain.com> Date: Wed, 21 Jan 2004 04:42:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00573.txt.bz2 > 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