This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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 / \


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]