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(get a core usable
with gdb).
- "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 this limit is for
RLIMIT_CORE im 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.
At 11:40 AM -0700 8/20/03, Yogeshwar Shenoy wrote:>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.Note that it would be better to ask questions about 5.1-RELEASE on the freebsd-current mailing list. The 5.x-series has not been made the "stable" branch of freebsd -- not yet at least. In a different message, Colin Faber wrote:> >Dual 2.4GHz Xeon P4 HT CPU's and I've discovered I can lock >up FreeBSD 5.1-RELEASE-p2 on commandSame for 5.x, for any value of '.x'. These are fine questions to ask for help on, it's just that you will get better results by asking the group of people who run the 5.x-series. freebsd-stable is still for the 4.x-series of releases. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu