From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: Krzysztof.Wisniowski@siemens.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: No core dump
Date: Thu, 30 Oct 2003 12:26:00 -0000 [thread overview]
Message-ID: <87oevzc4lb.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <2F09BBC1B282B64980E39E3DB109203506B92A@WROS222A>
Krzysztof.Wisniowski@siemens.com writes:
> Recently I had to switch to gcc 3.2. My program crashes with
> segmentation fault, however no core is dumped. Is there some
> compiler option to force the system to generate the core file, or is
> it system feature?
That's a system feature. Check ulimit, and make sure the current
working directory is writeable.
--
Falk
next prev parent reply other threads:[~2003-10-30 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 11:55 Krzysztof.Wisniowski
2003-10-30 12:26 ` Falk Hueffner [this message]
2003-10-30 12:03 Lev Assinovsky
2003-10-30 12:24 ` Segher Boessenkool
2003-10-30 12:33 ` Eljay Love-Jensen
2003-10-30 12:44 ` Claudio Bley
2003-10-30 12:31 Ajay Bansal
2003-10-30 12:50 Lev Assinovsky
2003-10-30 12:54 ` Mihnea Balta
2003-10-30 14:04 HOLTZ, CORBIN L. (JSC-ER) (LM)
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=87oevzc4lb.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.de \
--cc=Krzysztof.Wisniowski@siemens.com \
--cc=gcc-help@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).