From owner-freebsd-stable Tue Apr 9 6: 7:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-203.zoominternet.net [24.154.28.203]) by hub.freebsd.org (Postfix) with ESMTP id 16ADF37B41C for ; Tue, 9 Apr 2002 06:07:40 -0700 (PDT) Received: from topperwein (topperwein [192.168.168.10]) by topperwein.dyndns.org (8.11.6/8.11.6) with ESMTP id g39D7e305783 for ; Tue, 9 Apr 2002 09:07:40 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Tue, 9 Apr 2002 09:07:35 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: Unsopported relocation type? In-Reply-To: <038401c1df8f$087d20a0$01000001@ooe.kmjeuro.com> Message-ID: <20020409090542.R5710-100000@topperwein.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 9 Apr 2002, Karl M. Joch wrote: > Hello, > > i got that one on a freebsd 4.5 server running mostly only samba 2.2.3a with > about 50 workstations. > > /usr/libexec/ld-elf.so.1: > /usr/lib/libcrypto.so.2: Unsupported relocation type 85 in non-PLT > relocations PLT == Procedure Linkage Table Supposedly, this type of error can occur when non-PIC code is linked into a shared object. It could also be caused by a non-corrected bit error in memory (cosmic ray at an inopportune time while the rtld was doing its thing?). If it's not repeatable, don't worry about it--I've only seen it once in more than a dozen years myself, and it wasn't reproduceable. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message