On Tuesday March 05 1996 at 17:57, Peter Fitzsimmons wrote to Coridon Henshaw:

 PF> However --- the fact that exit() is getting stuck may be a sign that
 PF> there is a bug in your program -- for example,  the heap is corrupted.

I stepped through the exit()'s code and it was getting stuck in a memory-free loop.

 PF> Try calling _heapchk [or whatever your compiler provides] just before the
 PF> exit() and see what it has to say.

Been there, done that.  Heapchk returns OK.

It turns out that I was malloc()ing memory in a DLL and fiddling with it
using realloc() and free() it in the .EXE -- something that Watcom doesn't
like at all.  I'm statically linking the (former) DLL code with the rest of
the program to avoid this problem.

(I know, I know, freeing memory in a different program source file than it
was allocated is generally considered a design flaw, but I couldn't think
of any other way to do it.)

--- GoldED/2 2.50 UNREG