Date: Tue, 10 Jan 2006 19:02:30 +0200 From: Adi Pircalabu <apircalabu@bitdefender.com> To: "Paul Khavkine" <paul.khavkine@distributel.ca> Cc: freebsd-questions@freebsd.org Subject: Re: Abort signal Message-ID: <20060110190230.22c63818@apircalabu.dsd.ro> In-Reply-To: <1136908166.45759.0.camel@paul> References: <1136835510.44457.5.camel@paul> <2A6E6A56-4512-4F2D-9290-BD0D1599D34D@mac.com> <1136836338.44457.9.camel@paul> <D872E6A6-895B-4E78-A7AB-623339A7C3CF@mac.com> <1136908166.45759.0.camel@paul>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Jan 2006 10:49:26 -0500 "Paul Khavkine" <paul.khavkine@distributel.ca> wrote: > > > Hi Chuck. > > Ran memtest86 over night and no memory errors. > > > Any other ideas ? Maybe some sysctl magic? See below: $ ./a.out Abort trap: 6 (core dumped) # sysctl -w kern.coredump=0 kern.coredump: 1 -> 0 $ ./a.out Abort trap: 6 (No corefile here, see?) # sysctl -w kern.coredump=1 kern.coredump: 0 -> 1 $ ./a.out Abort trap: 6 (core dumped) > > Thanx > Paul > > On Mon, 2006-01-09 at 15:22 -0500, Charles Swiger wrote: > > On Jan 9, 2006, at 2:52 PM, Paul Khavkine wrote: > > > When i do that it crashes also but produces gdb.core > > > The backtrace form that doesn't tell me anything about where it > > > happends. > > > > If gdb itself crashes, I would suspect you've got hardware > > problems like bad memory. Try running memtest86.org's RAM tester > > overnight and see whether it picks up anything... > > -- Adi Pircalabu (PGP Key ID 0x04329F5E) -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060110190230.22c63818>