Hello Peter!

Replying to a message of Peter Fitzsimmons to Erik Huelsmann:

 EH>> What I was wondering is the following: When writing a 
 EH>> dll that might be used for multiple threads, I want to
 PF> I assume you mean different threads from the same process,  since one
 PF> thread from each of many processes is easy to cleanup after (the
 PF> system does it for you if your dll is "INITINSTANCE/TERMINSTANCE".
Yes, I did. (and indeed my dll is initinstance terminstance).

 EH>> have different variables (possibly with the same name, 
 EH>> as they are passed in strings) for different threads. 
 EH>> Is there a way to detect a thread has stopped and 
 EH>> should disallocate the memory?

 PF> Install an exception handler (see DosSetExceptionHandler) and look for
 PF> the XCPT_PROCESS_TERMINATE and XCPT_ASYNC_PROCESS_TERMINATE
 PF> exceptions (these are called when a thread dies,  not the whole
 PF> process as the name might imply).
Ok, I will do so. 

Do you know if a thread can dy from 'unnatural causes' without having the
entire process stopped? Ie I mean that I would like to know if has a fatal
exception, that the hole process has to dy with it, or if the rest of the
process can run on...


Bye, Erik!


 *** I am slowly getting there, but Sibyl is getting me there faster :-)
 *** Q's? e-mail me at ErikH{at}hcc-gron.idn.nl

---