Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!ginosko!uunet!mcsun!ukc!newcastle.ac.uk!turing!mccue
From: mccue@turing.newcastle.ac.uk (Dan McCue)
Newsgroups: comp.unix.wizards
Subject: Re: Reading the symbol table of the currently running executable
Message-ID: <1989Sep14.134546.2497@newcastle.ac.uk>
Date: 14 Sep 89 13:45:46 GMT
References: <9104@june.cs.washington.edu> <6131@lynx.UUCP> <LIMES.89Sep7153103@ouroborous.wseng.sun.com> <920@aoa.UUCP>
Sender: news@newcastle.ac.uk
Organization: Computing Laboratory, U of Newcastle upon Tyne, UK NE17RU
Lines: 17


    Recent discussions on the net about a program's inability to find out
    the name of the running executable point up a deficiency in the
    OS interface of UNIX(s).  Of course, on systems that support dynamic
    loading, this problem generalizes to finding out the name of 
    ALL of the executable images in an address space (and where they are 
    loaded).  The only UNIX operating system I am aware of that
    provides this service (reliably, in user mode) is Apollo's Domain/OS.

    Two questions:

    Are there other systems that provide a "system service" for finding
    the (path)name/load map of the running executable(s)?

    Are any of the UNIX standardization bodies either official (e.g.,
    POSIX, X/OPEN) or unoffical (e.g., OSF, Unix International) working
    on this problem?