From owner-freebsd-current Tue Sep 1 20:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26335 for freebsd-current-outgoing; Tue, 1 Sep 1998 20:46:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26327 for ; Tue, 1 Sep 1998 20:46:10 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-127.camalott.com [208.229.74.127]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA31774; Tue, 1 Sep 1998 22:46:57 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA03118; Tue, 1 Sep 1998 22:22:37 -0500 (CDT) (envelope-from joelh) Date: Tue, 1 Sep 1998 22:22:37 -0500 (CDT) Message-Id: <199809020322.WAA03118@detlev.UUCP> To: green@unixhelp.org CC: current@FreeBSD.ORG In-reply-to: (message from Brian Feldman on Tue, 1 Sep 1998 07:33:33 -0400 (EDT)) Subject: Re: E-day problems: rtld-elf dlsym() broken? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As a start, I'd like to say great job to John Birrell and everyone > else involved, going to ELF worked almost without a hitch, I'm > impressed! But there is a problem now: dlsym, for me, seems to have > stopped working. Entirely.... Returning NULL always it seems. I've > attached a program (yes, it's a start on a basic debugger, I'm > implementing rtld functions first) which should show the problem to > anyone interested. Guys, can we *please* start sending code snippets as plain text? MIME attachments are fine, just don't use base64. I will usually give code in plain text in a message a once-over, but it's more of a hassle to do so in base64. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message