From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9109 invoked by alias); 26 Sep 2003 16:44:07 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9084 invoked from network); 26 Sep 2003 16:44:06 -0000 Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89) by sources.redhat.com with SMTP; 26 Sep 2003 16:44:06 -0000 Received: by hawaii.kealia.com (Postfix, from userid 2049) id 77203CB31; Fri, 26 Sep 2003 09:44:06 -0700 (PDT) To: gdb Subject: core files in testsuite directory From: David Carlton Date: Fri, 26 Sep 2003 17:40:00 -0000 Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-09/txt/msg00321.txt.bz2 My testsuite directory is littered with core files. They're from annota1, annota3 (the one in gdb.base, not the one in gdb.cp), and signals. The first two tests attempt to remove a file named 'core', but the core files are actually named 'core.PID', so they stay around. Some questions: * I assume that all these tests are generating core files for legitimate reasons? It's not entirely clear to me why they're being generated, but I don't really understand what signals lead to core files in the first place. Assuming that's the case, we should presumably change the core file cleanup function (and move it to lib/gdb.exp, for ease of sharing, and have signals.exp call it as well). So: * What should the new cleanup function do? Should it just try to remove core.*? Or should it be passed the PID of the process in question, and only try to remove core.PID and core? David Carlton carlton@kealia.com