Date: Sat, 24 Nov 2001 00:52:55 +0100 From: Cliff Sarginson <cliff@raggedclown.net> To: questions@freebsd.org Subject: Re: .CORE files Message-ID: <20011124005255.A1087@raggedclown.net> In-Reply-To: <5.1.0.14.0.20011123185020.030944e0@mail.enterit.com> References: <20011123182901.A529@prayforwind.com> <5.1.0.14.0.20011123185020.030944e0@mail.enterit.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 23, 2001 at 06:55:03PM -0500, Jim Conner wrote: > At 18:29 11.23.2001 -0500, Steve Brown wrote: > 2. Netscape cores on probably everybody's machine at some time or > another. It is usually the result of poor coding (on Netscape's part) and > sometimes its the result of a poorly admin'ed system. In your case, I > would bet its netscapes code since I know a ton of people that get this > problem. It could also be a poorly set up Netscape that could cause > cores. Usually, the best thing to do is to remove the core file since its > really not needed for your sake. OR, you could send the core dumps to > Netscape so that they can examine why the core happened which is the > purpose of core dumps anyway. A core file is a physical readout of the > memory that netscape was using at the time it core'd. > Nah, don't be whimp, debug netscape .. lol..it is only about 10,000,000 lines of code. Netscape core dumps, hangs in strange ways, or just disappears on every platform I have used it on. I think it just gets tired; or more likely it's internal memory management is caboosh. -- Regards Cliff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011124005255.A1087>