I have come across what seems to me a particularly nasty situation.  I
write async communication DLLs in C that are used by a
non-communication-orinted program suite written in C++.  When I compile
the DLL in debug mode and then download some information (with the C++
program suite also compiled in debug mode), everything works well and I
have nothing but dollar signs in my eyes.  However, when I compile the
DLL in release mode (leaving the C++ program suite compiled in debug
mode) I can see that I royally tromp on memory which doesn't belong to
me (I _think_ this is the explaination, anyway).  Does anyone have any
suggestions as to the best (easiest and fastest) way to go about
debugging this quagmire?  Can anyone think of bugs which might be
common in such situations other than the one I think is obvious
(tromping on global heap space by writing to an array offset beyond the
limits given the array in question)?
 * KWQ/2 1.2i *
--- FLAME v1.1
---------------