Date: Fri, 29 Oct 1999 10:07:14 +0300 From: Maxim Sobolev <sobomax@altavista.net> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: ld-elf.so.1 (or VM?) weirdness Message-ID: <381947A2.6753C4C7@altavista.net> References: <3818467A.EA4DB1DE@altavista.net> <199910281656.JAA04489@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra wrote:
> In article <3818467A.EA4DB1DE@altavista.net>,
> Maxim Sobolev <sobomax@altavista.net> wrote:
>
> > For a quite long time I searched for the way to reproduce this bug,
> > and it seems that I've finally found how to do it. In most cases
> > attempt to make any port on a freshly booted system stops with:
> >
> > /usr/libexec/ld-elf.so.1: /usr/bin/awk: Shared object has no run-time symbol
> > table
> >
> > but when I'm trying to run make again with the same port it works
> > flawlessly.
>
> I haven't heard any other reports of this. I'm almost certain it is
> caused by something outside the dynamic linker -- probably a kernel
> bug. The debugging output you included shows evidence that the
> dynamic linker is seeing garbage when it mmaps your executable. The
> fact that it works OK after the first attempt also points to the VM
> system as the culprit. The dynamic linker hasn't changed much
> recently, but the kernel has changed a lot.
Ok, but why it affects only linker and what in your opinion best course of actions
would be to reveal reason of this misbehaviour?
-Maxim
--
"We believe in the Power and the Might!"
(Manowar, 1996)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?381947A2.6753C4C7>