This is the mail archive of the gdb@sourceware.org mailing list for the GDB 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: Empty core dump file

From: David Aldrich <David dot Aldrich at EMEA dot NEC dot COM>
To: Baurzhan Ismagulov <ibr at radix50 dot net>, "gdb at sourceware dot org" <gdb at sourceware dot org>
Date: Fri, 26 Aug 2011 13:46:01 +0000
Subject: RE: Empty core dump file
References: <41302A7145AC054FA7A96CFD03835A0A047BD8@EX10MBX02.EU.NEC.COM> <20110826131657.GW25065@radix50.net>

> On Fri, Aug 26, 2011 at 12:35:59PM +0000, David Aldrich wrote:
> > When my C++ program crashes with a segmentation fault I get an empty
> > core dump file called core.13754.
> ...
> > ulimit -c unlimited
> 
> I wouldn't expect any problems if you don't get an error message after this
> command, but I'd double-check ulimit -Sc and ulimit -Hc outputs.

$ ulimit -Sc
unlimited
$ ulimit -Hc
unlimited

> > Why might the core dump be empty?
> 
> You do have space on the device, don't you?

Yes, but I have just realised that I am working on a shared drive from a VM. There may be some permissions problem. I will check.

> Is this i386?

It's a 64-bit Linux VM.

Thanks for your help.

David

References:
- Empty core dump file
  - From: David Aldrich
- Re: Empty core dump file
  - From: Baurzhan Ismagulov

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