Path: utzoo!attcan!utgpu!watmath!att!icus!lenny
From: lenny@icus.islp.ny.us (Lenny Tropiano)
Newsgroups: unix-pc.general
Subject: Re: Large programs core dumping upon execution
Summary: Check your /usr/adm/unix.log file!
Message-ID: <929@icus.islp.ny.us>
Date: 27 Jul 89 00:57:05 GMT
References: <211@comhex.UUCP>
Reply-To: lenny@icus.islp.ny.us (Lenny Tropiano)
Distribution: unix-pc
Organization: ICUS Software Systems, Islip, New York
Lines: 27

In article <211@comhex.UUCP> sysop@comhex.UUCP (Joe E. Powell) writes:
|>Has anyone else ever noticed that very large (over 300K) files
|>sometimes tend to core dump when they are invoked?  They usually
|>work fine, but every now and again, the program will just refuse
|>to start up.  Is it just me or have other people had this happen?
|>
|>I've noticed this occasionally on nethack and moria, but more
|>often with gcc (esp gcc 1.35).
|>
|>I'm running 3.51a, with a 40 MB drive and 2.5 MB of RAM.

I would check the output (if any) in your /usr/adm/unix.log file.  It 
is possible you are getting NMI Parity errors (if your program core dumps
with a "Memory Fault" this kinda sounds like the symptoms)   This usually
signifies bad memory (sorry to say) ... Run memory diagnostics, although
that doesn't always find the problem.   I'd also suggest pulling the .5MB
of RAM out, and see if it goes away ... (possibly the bad memory is on
the expansion board).

Good luck!

-Lenny
-- 
Lenny Tropiano             ICUS Software Systems         [w] +1 (516) 589-7930
lenny@icus.islp.ny.us      Telex; 154232428 ICUS         [h] +1 (516) 968-8576
{ames,talcott,decuac,hombre,pacbell,sbcs}!icus!lenny     attmail!icus!lenny
        ICUS Software Systems -- PO Box 1; Islip Terrace, NY  11752