From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24178 invoked by alias); 24 Sep 2004 19:05:59 -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 23961 invoked from network); 24 Sep 2004 19:05:54 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 24 Sep 2004 19:05:54 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8OJ5nhj003827 for ; Fri, 24 Sep 2004 15:05:49 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8OJ5hr02777; Fri, 24 Sep 2004 15:05:43 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id A3E6128D2; Fri, 24 Sep 2004 15:03:27 -0400 (EDT) Message-ID: <41546F7F.7020906@gnu.org> Date: Fri, 24 Sep 2004 19:05:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040831 MIME-Version: 1.0 To: Michael Chastain Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa/testsuite] Get the inferior to dump core References: <414EE841.7080908@gnu.org> <4152F35E.nail1HN1VVA80@mindspring.com> <41531588.3040308@gnu.org> <41532A21.nail51S19TWYK@mindspring.com> <41546089.9020704@gnu.org> <415468D2.nail1GB11NHJS@mindspring.com> In-Reply-To: <415468D2.nail1GB11NHJS@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00413.txt.bz2 > I'm not too worried about the interface (!), it's standardizing > the guts that I'm worried about. I was thinking that bigcore.exp's could be moved to gdb.exp where they can be used by other corefile tests with that bug - worry about fancying the guts if/when there's a need. Andrew > - portable way to set the core dump size to "unlimited". > i suspect this is more portable to do at the C level with > setrlimit() rather than the shell level with the bitter > comments about braindamaged shells and ulimit. > > - creating a subdirectory > corefile.exp does this at the TCL level, which immediately > runs into a build != host problem. Again I suspect this > might be better to do in the inferior program: > mkdir("coredir"); > chdir("coredir"); > coredir does not have to be unique. > > - picking up the core file > there should be exactly ONE file in coredir. If there are > zero files, or two more files, then the test script cannot > proceed. > > The problem is figuring out the name of that file. > It's on the host machine so just "glob" will not cut it. > I don't know if there's a "remote glob" available or what. > > After figuring out the name of the file, do remote_upload > to get it back to the build machine to a fixed name. > > That's just a half-assed look at gcore.exp. > > Now, is it worth anyone's time to actually do this? > > I don't want to get into it myself because I want to get into > "user specifies which compiler to run for each language". > That's high priority and it's a big overhaul.