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: Fri, 24 Sep 2004 19:05:00 -0000 [thread overview]
Message-ID: <41546F7F.7020906@gnu.org> (raw)
In-Reply-To: <415468D2.nail1GB11NHJS@mindspring.com>
> I'm not too worried about the interface (!), it's standardizing
> the guts that I'm worried about.
I was thinking that bigcore.exp's could be moved to gdb.exp where they
can be used by other corefile tests with that bug - worry about fancying
the guts if/when there's a need.
Andrew
> - 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.
prev parent reply other threads:[~2004-09-24 19:05 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
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 [this message]
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=41546F7F.7020906@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