From owner-freebsd-current Fri Oct 29 0: 8: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4DEA814CB8 for ; Fri, 29 Oct 1999 00:07:52 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup3-39.iptelecom.net.ua [212.42.74.167]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA14685; Fri, 29 Oct 1999 10:10:23 +0300 (EEST) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA58102; Fri, 29 Oct 1999 10:07:15 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <381947A2.6753C4C7@altavista.net> Date: Fri, 29 Oct 1999 10:07:14 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John Polstra Cc: current@freebsd.org Subject: Re: ld-elf.so.1 (or VM?) weirdness References: <3818467A.EA4DB1DE@altavista.net> <199910281656.JAA04489@vashon.polstra.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <3818467A.EA4DB1DE@altavista.net>, > Maxim Sobolev 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