Date: Mon, 20 Jun 2005 19:07:48 -0400 (EDT) From: Tuc at T-B-O-H <ml@t-b-o-h.net> To: dmitry.mityugov@gmail.com Cc: Tuc at T-B-O-H <ml@t-b-o-h.net>, freebsd-questions@freebsd.org Subject: Re: Problems since 5.3-RELEASE-p15 Message-ID: <200506202307.j5KN7mnB000906@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <b7052e1e0506190027d801899@mail.gmail.com> from "Dmitry Mityugov" at Jun 19, 2005 11:27:10 AM
next in thread | previous in thread | raw e-mail | index | archive | help
> > On 6/17/05, Tuc at T-B-O-H <ml@t-b-o-h.net> wrote: > > Hi, > > > > Ever since I upgraded to 5.3-RELEASE-p15, I've started to run into > > problems... All of a sudden, anything I do results in a Segfault. Sometimes > > I'll get : > > > > /libexec/ld-elf.so.1: top: Shared object has no run-time symbol table > > Is there a more or less reliable way to reproduce this? What should I > run to try to reproduce this? > Thats the thing. I can't force it to happen. It just "does". Infact, when looking at my logs, it happened at 1am this morning and I didn't even realize it (And wasn't anywhere near the machine). I can't do any debugging once it starts since EVERYTHING cores that I try to run..... This isn't a production server so I'm not dying for a solution, but it would be nice to not have this problem. Thanks, Tuc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506202307.j5KN7mnB000906>