From owner-freebsd-current Wed Mar 20 10:15:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 988F937B416 for ; Wed, 20 Mar 2002 10:15:27 -0800 (PST) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.11.6/8.11.6) with UUCP id g2KIFBI49430; Wed, 20 Mar 2002 18:15:11 GMT (envelope-from mark@grimreaper.grondar.za) Received: from grimreaper (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.2/8.12.2) with ESMTP id g2KIEt4j070444; Wed, 20 Mar 2002 18:14:55 GMT (envelope-from mark@grimreaper.grondar.za) Message-Id: <200203201814.g2KIEt4j070444@grimreaper.grondar.org> To: Miguel Mendez Cc: current@FreeBSD.ORG Subject: Re: rtld messing up? References: <20020320185537.B86169@energyhq.homeip.net> In-Reply-To: <20020320185537.B86169@energyhq.homeip.net> ; from Miguel Mendez "Wed, 20 Mar 2002 18:55:37 +0100." Date: Wed, 20 Mar 2002 18:14:55 +0000 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > In ports/lang/gcl, a program is "undumped", and the resultant binary > > dumps core _very_ early in the startup. I can't get debugging info, > > because the undumping also seems to strip the program. > > I've also have had that same problem when I tried to build the port, > but was never able to find the reason for the program to segfault, I > even opened a PR on that. The program seems to work on NetBSD btw.=20 PR ports/34661 :-) M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message