From owner-freebsd-current@FreeBSD.ORG  Wed Aug 20 14:11:47 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3CA6B16A4BF
	for <freebsd-current@freebsd.org>;
	Wed, 20 Aug 2003 14:11:47 -0700 (PDT)
Received: from alumni.cs.ucsb.edu (alumni.cs.ucsb.edu [128.111.41.99])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8204643FD7
	for <freebsd-current@freebsd.org>;
	Wed, 20 Aug 2003 14:11:46 -0700 (PDT)
	(envelope-from ynshenoy@alumni.cs.ucsb.edu)
Received: (qmail 31422 invoked by uid 1037); 20 Aug 2003 21:11:18 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 20 Aug 2003 21:11:18 -0000
Date: Wed, 20 Aug 2003 14:11:18 -0700 (PDT)
From: Yogeshwar Shenoy <ynshenoy@alumni.cs.ucsb.edu>
To: freebsd-current@freebsd.org
Message-ID: <Pine.LNX.4.56L0.0308201406280.31072@alumni.cs.ucsb.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: 5.1-R: zero byte core file.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Aug 2003 21:11:47 -0000


While using 5.1-RELEASE, I find that if my application program seg 
faults, it produces "programname.core"; but it is 0 bytes.
I ran the exact same program on another machine that was running 
4.4-RELEASE, and I do get a core file that I can use with gdb.
I'd really appreciate if someone could help me resolve this.

Additional details: 
- It is not specific to the application program. I tried a 2 line program:
    char p[8];
    memcpy(p, "1234567890123456789012345678901234567890", 40);
 with same results on 5.1-R(0 byte core file) and 4.4-R(usable core file)

- "ulimit -a" on the 5.1-R machine gives
   core file size        (blocks, -c) unlimited

- Just to be sure I used getrlimit() to find what the limit  for 
RLIMIT_CORE is in my processes, and it is RLIM_INFINITY.

- I did the basic checks like write permission on current directory, it 
looks fine.

Can someone help me resolve this? 

Thanks,
Yogeshwar.