From owner-freebsd-current Wed Apr 3 11: 2: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id 7FF8637B41C for ; Wed, 3 Apr 2002 11:02:03 -0800 (PST) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id 02927C623; Wed, 3 Apr 2002 12:02:03 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id 6FC7512A; Wed, 3 Apr 2002 12:02:02 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id LAA12554; Wed, 3 Apr 2002 11:01:52 -0800 (PST) Message-Id: <200204031901.LAA12554@mina.soco.agilent.com> To: Mark Murray Cc: Miguel Mendez , current@FreeBSD.ORG Subject: Re: rtld messing up? Reply-To: Darryl Okahata In-Reply-To: Your message of "Wed, 20 Mar 2002 18:14:55 GMT." <200203201814.g2KIEt4j070444@grimreaper.grondar.org> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Wed, 03 Apr 2002 11:01:50 -0800 From: Darryl Okahata 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 Last month, Mark Murray wrote: > > > 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 :-) Has anyone gotten any further on this? I took a look at ports/34661, but nothing new has been added to it. Using 4-STABLE (sorry, I'm not using -current), I took a quick stab at the problem (having dealt with XEmacs undump issues in a past life), but I haven't gotten anywhere, yet: XEmacs uses unexelf.c, whereas gcl uses unexec.c. Changing gcl to use unexelf.c didn't change anything, but the next step is to compare the two unexelf.c's (they are different). The core stack trace seems to imply that there's some constructor initialization issue that undump isn't handling properly. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message