From: Daniel Jacobowitz <drow@mvista.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: core files in testsuite directory
Date: Fri, 26 Sep 2003 17:49:00 -0000 [thread overview]
Message-ID: <20030926174558.GA23276@nevyn.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2003-09-26 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 17:40 David Carlton
2003-09-26 17:49 ` Daniel Jacobowitz [this message]
2003-09-26 18:12 ` David Carlton
2003-09-26 21:19 ` Daniel Jacobowitz
2003-09-27 4:33 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030926174558.GA23276@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox