This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: core files in testsuite directory
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gdb <gdb at sources dot redhat dot com>
- Date: Fri, 26 Sep 2003 13:45:59 -0400
- Subject: Re: core files in testsuite directory
- References: <yf2vfrf7b55.fsf@hawaii.kealia.com>
On Fri, Sep 26, 2003 at 09:44:06AM -0700, David Carlton wrote:
> 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?
Check um... corefile.exp? Which does the former, I believe.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer