From owner-freebsd-questions Sat May 24 18:50:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA01038 for questions-outgoing; Sat, 24 May 1997 18:50:16 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA01031 for ; Sat, 24 May 1997 18:50:14 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id SAA27757; Sat, 24 May 1997 18:50:13 -0700 Date: Sat, 24 May 1997 18:50:13 -0700 From: Sean Eric Fagan Message-Id: <199705250150.SAA27757@kithrup.com> To: questions@freebsd.org Subject: Re: execve() and the actual name of the image executed Newsgroups: kithrup.freebsd.questions In-Reply-To: <199705250053.RAA16879.kithrup.freebsd.questions@implode.root.com> References: Your message of "Sat, 24 May 1997 16:01:22 PDT." <199705242301.QAA19073@precipice.shockwave.com> Organization: Kithrup Enterprises, Ltd. Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199705250053.RAA16879.kithrup.freebsd.questions@implode.root.com> you write: >>Is there any /absolutely guaranteed/ way to get a pointer to the/a path >>that was actually used to invoke an image from that image? > /proc//file is one way. This only works on FreeBSD 2.2+, however. And that is one of the reasons that node is in procfs :). (The *main* reason is so you can get symbols from any process you wish to debug, without knowing the actual name of the file.) Sean.