Xref: utzoo comp.sys.ibm.pc.programmer:1389 alt.msdos.programmer:1615
Path: utzoo!utgpu!cunews!bcars8!bnrgate!bigsur!bnr-rsc!mlord
From: mlord@bnr-rsc.UUCP (Mark Lord)
Newsgroups: comp.sys.ibm.pc.programmer,alt.msdos.programmer
Subject: Re: releasing the environment in tsrs
Message-ID: <2853@bnr-rsc.UUCP>
Date: 9 May 90 16:24:21 GMT
References: <489@wjh12.harvard.edu>
Reply-To: mlord@bnr-rsc.UUCP (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 21

In article <489@wjh12.harvard.edu> djb@wjh12.UUCP (David J. Birnbaum) writes:
>I recently added a routine to a tsr to release the environment
>...1) Memory mapping utilities can not identify the name of the program
>once the environment has been deallocated.  I suspect this is because
>they get the name from the undocumented file name appended to the
>environment; no environment = no file name.  Is there any way to
>coerce a program without an environment into reporting its name
>correctly to such utilities?

I usually set my environment ptr to point at a small allocated "dummy"
environment, containing nothing but the program name.  This works with
all memory mappers I have seen thus far.  The dummy env has to allocated
separately from the tsr if the tsr is ever to be unloaded, to avoid attempts
to deallocate the same space twice.

-Mark
-- 
 ______Mark S. Lord______________________ ______________________________
|    ..uunet!bnrgate!carrsc!mlord        | These are only MY opinions.  |
| or:  bnr-rsc!mlord@bnrgate             | I charge for official views. |
|________________________________________|______________________________|