From owner-freebsd-hackers Sun Jan 18 10:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02185 for hackers-outgoing; Sun, 18 Jan 1998 10:51:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02172 for ; Sun, 18 Jan 1998 10:51:04 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA14188; Sun, 18 Jan 1998 09:50:26 -0800 (PST) (envelope-from jdp) Message-Id: <199801181750.JAA14188@austin.polstra.com> To: Terry Lambert Cc: hasty@rah.star-gate.com, hackers@FreeBSD.ORG Subject: Re: dladdr hax In-reply-to: Your message of "Sun, 18 Jan 1998 06:53:04 GMT." <199801180653.XAA07823@usr04.primenet.com> Date: Sun, 18 Jan 1998 09:50:25 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > To be bug-compatible with Solaris, you should simply return argv[0] > *witjout* trying to find it in your PATH. Really?! Gawd, what a hack. Well, that's easy, anyway. > Yes, this is a kludge. The whole dladdr interface reeks of, shall we say, expediency. I particularly loathe the requirement that it also return the "nearest symbol name to the specified address." I wish they had made that optional. It's very expensive, requiring a linear search of the whole symbol table. And I bet it's not even used most of the time. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth