From owner-freebsd-hackers Sat Jan 17 14:32:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28563 for hackers-outgoing; Sat, 17 Jan 1998 14:32:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd1.cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28542 for ; Sat, 17 Jan 1998 14:31:58 -0800 (PST) (envelope-from jb@freebsd1.cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.8.7/8.8.7) id JAA15804; Sun, 18 Jan 1998 09:37:42 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199801172237.JAA15804@freebsd1.cimlogic.com.au> Subject: Re: dladdr hax In-Reply-To: <199801172227.OAA06497@rah.star-gate.com> from Amancio Hasty at "Jan 17, 98 02:27:17 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 18 Jan 1998 09:37:42 +1100 (EST) Cc: jdp@polstra.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Amancio Hasty wrote: > Not sure that I understand whats going on . when the kernel loads > an image it has the full path so the question now is where do > we save the path -- the most intuitive place is the proc > structure. I would have thought so too, but I'm not a kernel hacker. 8-) I've got applications that would benefit from being able to find out where they were executed from. Regards, -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137