From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26928 invoked by alias); 24 Sep 2004 18:34:41 -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 26880 invoked from network); 24 Sep 2004 18:34:39 -0000 Received: from unknown (HELO tisch.mail.mindspring.net) (207.69.200.157) by sourceware.org with SMTP; 24 Sep 2004 18:34:39 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by tisch.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1CAutx-0007HQ-00; Fri, 24 Sep 2004 14:34:37 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id DB7304B102; Fri, 24 Sep 2004 14:34:58 -0400 (EDT) Date: Fri, 24 Sep 2004 18:34:00 -0000 From: Michael Chastain To: cagney@gnu.org Subject: Re: [rfa/testsuite] Get the inferior to dump core Cc: gdb-patches@sources.redhat.com Message-ID: <415468D2.nail1GB11NHJS@mindspring.com> References: <414EE841.7080908@gnu.org> <4152F35E.nail1HN1VVA80@mindspring.com> <41531588.3040308@gnu.org> <41532A21.nail51S19TWYK@mindspring.com> <41546089.9020704@gnu.org> In-Reply-To: <41546089.9020704@gnu.org> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00411.txt.bz2 I'm not too worried about the interface (!), it's standardizing the guts that I'm worried about. - 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.