andhal@auto-trol.UUCP (Andrew Halls) (06/20/89)
I'm having trouble finding a bug in my windows application. The symptoms move
around as I change this or that. I think I'm trashing some part of Windows.
Is there some way to either check to state of Windows or bound my memory references
to only user portions of memory while debugging?
more details:
I'm currently using the latest development tools:
MSC 5.1
SDK 2.?
XVT 1.2.1 This is a virtual windows toolkit, which is currently complicating my
trouble shooting efforts. The area that I am having trouble is outside
of this toolkit's capablility so I'm using MS Windows calls directly.
I have been very carefull to check the return status of every windows function that
I use.
The current symptom is that the BitBlt function does not change what is seen on the
display and when I exit the program Windows displays a divide by zero dialog box.
Sometimes everything hangs when I try to free global memory.
If I reorganize my code, none of the changes "should" be material to Windows, I
get other symptoms. For example: the display works fine, but everything hangs
after 20 minutes of operation, the exact sequence I haven't duplicated....
I would appreciate any suggestions.
Andy Halls
{...}ncar!ico!auto-trol!andhal Auto-trol Technology Corporation
12500 North Washington Street
(303)-252-2166 Denver, CO 80241-2404
--
Andy Halls
{...}ncar!ico!auto-trol!andhal Auto-trol Technology Corporation
12500 North Washington Street
(303)-252-2166 Denver, CO 80241-2404