From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: <Krzysztof.Wisniowski@siemens.com>, <gcc-help@gcc.gnu.org>
Subject: RE: No core dump
Date: Thu, 30 Oct 2003 12:03:00 -0000 [thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D62014B7321@bagman.edm.com> (raw)
If your system is Linux then "no coredump" is a feature.
I heard to fix that you have to recompile the kernel.
----
Lev Assinovsky
Aelita Software Corporation
O&S InTrust Framework Division, Team Leader
ICQ# 165072909
> -----Original Message-----
> From: Krzysztof.Wisniowski@siemens.com
> [mailto:Krzysztof.Wisniowski@siemens.com]
> Sent: Thursday, October 30, 2003 2:55 PM
> To: gcc-help@gcc.gnu.org
> Subject: No core dump
>
>
> Hi all,
> 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?
>
> Greetings,
> --
> Krzysztof Wisniowski | Siemens Sp. z o.o.
> ICM SDC NMR 3 | Software Design Center
> Phone: +48 71 799 2403 | 54A Strzegomska Str.
> Fax: +48 71 799 2320 | 53-611 Wroclaw POLAND
>
>
next reply other threads:[~2003-10-30 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 12:03 Lev Assinovsky [this message]
2003-10-30 12:24 ` Segher Boessenkool
2003-10-30 12:33 ` Eljay Love-Jensen
2003-10-30 12:44 ` Claudio Bley
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 14:04 HOLTZ, CORBIN L. (JSC-ER) (LM)
2003-10-30 12:50 Lev Assinovsky
2003-10-30 12:54 ` Mihnea Balta
2003-10-30 12:31 Ajay Bansal
2003-10-30 11:55 Krzysztof.Wisniowski
2003-10-30 12:26 ` Falk Hueffner
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=3F6F4712B759A34ABD453A8B39C10D62014B7321@bagman.edm.com \
--to=lassinovsky@algorithm.aelita.com \
--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).