public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/10628: core file not generated
Date: Tue, 06 May 2003 08:26:00 -0000 [thread overview]
Message-ID: <20030506082640.10852.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/10628; it has been noted by GNATS.
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
khan_sanjay@operamail.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: other/10628: core file not generated
Date: Tue, 6 May 2003 10:17:07 +0200
On Mon, May 05, 2003 at 02:34:51PM -0000, bangerth@dealii.org wrote:
> Creation of core files is not controlled by the compiler, but
> by the shell. Use for example ulimit.
The shell may play a role, but the application can catch SIGSEGV and
exit instead of dumping core. IIRC this is what gcc does and IMHO it is
a valid feature request that gcc should have an option to actually
make the backends dump core.
regards Christian
--
THAT'S ALL FOLKS!
next reply other threads:[~2003-05-06 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 8:26 Christian Ehrhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 15:06 Andrew Pinski
2003-05-06 15:03 bangerth
2003-05-06 14:26 Andrew Pinski
2003-05-06 14:26 Wolfgang Bangerth
2003-05-06 14:09 bangerth
2003-05-05 14:34 bangerth
2003-05-05 13:36 khan_sanjay
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=20030506082640.10852.qmail@sources.redhat.com \
--to=ehrhardt@mathematik.uni-ulm.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).