Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] Get the inferior to dump core
Date: Thu, 23 Sep 2004 18:29:00 -0000	[thread overview]
Message-ID: <41531588.3040308@gnu.org> (raw)
In-Reply-To: <4152F35E.nail1HN1VVA80@mindspring.com>

> This patch is approved.

Tks, I'll commit shortly.

> I had wondered about that technique of bigcore.exp, it surprised me a
> bit when I saw that it was making two runs of the inferior.
> 
> 
>>> Is this ok?  I just wonder if it should be generalized and moved to 
>>> gdb.exp, I guess that should be a separate pass.
> 
> 
> I don't know exactly what "it" is referring to, but a separate pass
> for moving "it" to gdb.exp sounds good to me.

The sequence needed to first generate and then locate/rename a corefile 
from an inferior running under GDB (instead of running the program twice).

> I like what corefile.exp tries to do.  It creates a unique subdirectory
> and runs the target program in the subdirectory so that the core file
> is easy to find.  It suffers from build != host problems though.

but it (and I'm sure there are others) suffers from corefile != inferior 
problems and I'm pretty sure all duplicated corefile's logic.

Andrew



  reply	other threads:[~2004-09-23 18:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20 14:27 Andrew Cagney
2004-09-23 17:58 ` Michael Chastain
2004-09-23 18:29   ` Andrew Cagney [this message]
2004-09-23 19:55     ` Michael Chastain
2004-09-24 18:02       ` Andrew Cagney
2004-09-24 18:34         ` Michael Chastain
2004-09-24 19:05           ` Andrew Cagney

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=41531588.3040308@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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