From owner-freebsd-chat Tue Sep 1 23:37:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24952 for freebsd-chat-outgoing; Tue, 1 Sep 1998 23:37:55 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24921 for ; Tue, 1 Sep 1998 23:37:47 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA00931; Wed, 2 Sep 1998 16:06:40 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA10083; Wed, 2 Sep 1998 16:06:34 +0930 (CST) Message-ID: <19980902160634.G606@freebie.lemis.com> Date: Wed, 2 Sep 1998 16:06:34 +0930 From: Greg Lehey To: joelh@gnu.org, green@unixhelp.org Cc: FreeBSD Chat Subject: Re: E-day problems: rtld-elf dlsym() broken? References: <199809020322.WAA03118@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199809020322.WAA03118@detlev.UUCP>; from Joel Ray Holveck on Tue, Sep 01, 1998 at 10:22:37PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 X-Mutt-References: <199809020322.WAA03118@detlev.UUCP> Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (moved to -chat) On Tuesday, 1 September 1998 at 22:22:37 -0500, Joel Ray Holveck wrote: >> 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. Can't pine autodecode base64 transparently? It seems to me that we should agree on some base set of functionality that a reasonable mailer should support. Most reasonable mailers support MIME nowadays, but the level of support varies considerably (that's one of the reasons I moved from elm; when I tried pine, I didn't have any trouble with MIME, but I just didn't like some of the things it did). I'll toss in a couple of features for discussion: 1. MIME 2. base 64 3. 8 bit code 4. html 5. PostScript 6. RTF (can anybody decipher it?) 7. images Any others? Any comments? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message