Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!news.cs.indiana.edu!know!newmedia!jim
From: jim@newmedia.UUCP (Jim Beveridge)
Newsgroups: comp.windows.ms.programmer
Subject: Windows hanging & DLL problems
Message-ID: <449@newmedia.UUCP>
Date: 22 Mar 91 04:00:23 GMT
Organization: New Media Graphics, Billerica, MA
Lines: 35

Help!!!  I am completely stumped by a problem that I have run into.

I am developing two DLLs and an application.  The application calls
the first DLL, which then calls the second.  All DLL's are explicitly
linked at LINK time.   Optimization is disabled.

The first time I run the application, everything works just fine.  
If I try and run it again, the system hangs.  The mouse still 
moves, but that's about it.  Before the 2nd run, I can start an 
application like the heap walker without any trouble.  The moment 
I launch the application the second time, kaboom.

Even more bizarre is the fact that I can make sure that none of
the functions in the DLL are called so that they will be loaded
but not executed, and the program will still die with the same 
behavior.  This leads me to believe the problem is in LibMain 
or the WEP, but these are the bare minimum functions 
(ie.  They both just return 1).

I am utterly baffled.  The problem has been randomly appearing and
disappearing over the past few weeks, depending on how optimization
and debugging are set, but now the problem persists no matter how
I set the options.  It is even doing things like working fine if I
use the debugging version of Windows and crashing under the normal
version.

If anyone has any ideas, or you need more information,
please send me mail or give me a call.

Thanks, Jim Beveridge

-----------------------------------------------------------------
email:  ..!uunet!know!newmedia.UUCP!jim
phone:	(508) 663-0666
-----------------------------------------------------------------