From: Mihnea Balta <dark_lkml@mymail.ro>
To: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>,
"Claudio Bley" <bley@cs.uni-magdeburg.de>
Cc: <Krzysztof.Wisniowski@siemens.com>, <gcc-help@gcc.gnu.org>
Subject: Re: No core dump
Date: Thu, 30 Oct 2003 12:54:00 -0000 [thread overview]
Message-ID: <200310301455.23503.dark_lkml@mymail.ro> (raw)
In-Reply-To: <3F6F4712B759A34ABD453A8B39C10D62014B735F@bagman.edm.com>
It's not the compiler's job to produce a core dump. Redhat disables core
dump from one of its startup scripts. Just tipe "ulimit -c unlimited" before
running the faulty program.
On Thursday 30 October 2003 14:49, Lev Assinovsky wrote:
> I know for sure that in RedHat 8.x, 9.x gcc doesn't produce core dump.
>
> ----
> Lev Assinovsky
> Aelita Software Corporation
> O&S InTrust Framework Division, Team Leader
> ICQ# 165072909
>
> > -----Original Message-----
> > From: Claudio Bley [mailto:bley@cs.uni-magdeburg.de]
> > Sent: Thursday, October 30, 2003 3:42 PM
> > To: Lev Assinovsky
> > Cc: Krzysztof.Wisniowski@siemens.com; gcc-help@gcc.gnu.org
> > Subject: Re: No core dump
> >
> > On Thu, Oct 30, 2003 at 03:02:50PM +0300, Lev Assinovsky wrote:
> > > If your system is Linux then "no coredump" is a feature.
> > > I heard to fix that you have to recompile the kernel.
> > >
> > > > -----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?
> >
> > I think you're talking about a kernel core dump. Normally Linux should
> > support core dumps of normal programs and I don't think there is an
> > option for that, I may be wrong though.
> >
> > You (Krzysztof) should just check your process resource limits which
> > you usually can check and adjust using your shell. E.g. in bash:
> >
> > $ ulimit -c # print core file size limit
> > 0 # <- don't generate core dumps
> > $ ulimit -c unlimited # always generate a core file
> > regardless how big it is
> >
> >
> > If you want to control this from your program, have a look at the
> > getrlimit and setrlimit functions.
> >
> > --
> > Claudio Bley ASCII ribbon campaign (")
> > Debian GNU/Linux user - against HTML email X
> > http://www.cs.uni-magdeburg.de/~bley/ & vCards / \
>
> ---------------------------------------------------------------
> Acasa.ro vine cu albumele, tu vino doar cu pozele ;)
> http://poze.acasa.ro/
next prev parent reply other threads:[~2003-10-30 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 12:50 Lev Assinovsky
2003-10-30 12:54 ` Mihnea Balta [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-30 14:04 HOLTZ, CORBIN L. (JSC-ER) (LM)
2003-10-30 12:31 Ajay Bansal
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 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=200310301455.23503.dark_lkml@mymail.ro \
--to=dark_lkml@mymail.ro \
--cc=Krzysztof.Wisniowski@siemens.com \
--cc=LAssinovsky@algorithm.aelita.com \
--cc=bley@cs.uni-magdeburg.de \
--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).