From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4580 invoked by alias); 30 Oct 2003 12:44:40 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 4533 invoked from network); 30 Oct 2003 12:44:37 -0000 Received: from unknown (HELO wh2-19.st.uni-magdeburg.de) (141.44.162.19) by sources.redhat.com with SMTP; 30 Oct 2003 12:44:37 -0000 Received: from bley by wh2-19.st.uni-magdeburg.de with local (Exim 3.36 #1 (Debian)) id 1AFC8A-00063y-00; Thu, 30 Oct 2003 13:42:26 +0100 Date: Thu, 30 Oct 2003 12:44:00 -0000 From: Claudio Bley To: Lev Assinovsky Cc: Krzysztof.Wisniowski@siemens.com, gcc-help@gcc.gnu.org Subject: Re: No core dump Message-ID: <20031030124226.GE6444@wh2-19.st.uni-magdeburg.de> Mail-Followup-To: Claudio Bley , Lev Assinovsky , Krzysztof.Wisniowski@siemens.com, gcc-help@gcc.gnu.org References: <3F6F4712B759A34ABD453A8B39C10D62014B7321@bagman.edm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F6F4712B759A34ABD453A8B39C10D62014B7321@bagman.edm.com> User-Agent: Mutt/1.5.4i X-SW-Source: 2003-10/txt/msg00444.txt.bz2 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 / \