wberger@bunker.UUCP (William Wonneberger) (10/11/90)
We are having problems debugging a rather large Windows 3.0
application running in 386 Enhanced Mode.
We can use CodeView for Windows to step through the code without any
problems, and the program terminates normally. However, after the
program has terminated, Windows 3.0 is completely hung.
(i.e., we cannot access any other Windows applications). In the upper
left hand corner of the screen, a there is a hole in the wallpaper
with a DOS prompt. The system is completely hung, and the only way to
clear things up is by powering off and on.
When we minimize the program, and run other Windows applications,
such as Power Point and Excel, and then resume running the program,
the program runs without a problem, again, until the program terminates.
Any information with regards to the following would be greatly appreciated:
- What would cause Windows 3.0 to hang completely
after a program terminates normally?
- Are there any caveats in the Windows 3.0 API on
dynamic memory allocation that might result in the
problem described above?
- Why would minimizing the program in question not affect
Windows 3.0, and not its termination?
- Can anyone make any suggestions on which API calls
we might look at when dealing with this problem?
Please reply by E-mail, and I will gladly post the replies to the
newsgroups.
Thank you in advance for your time and assistance.
wberger: William T. Wonneberger VOX: (203) 337-1624
ISC-Bunker Ramo Olivetti FAX: (203) 337-1649
Associate Engineer VAX: ...{oliveb,isc-br,philabs,yale,
Product Development decvax}!bunker!wberger
wberger@Bunker.UUCP
"Go with the flow until you get an XOF..."
------------------------------------------------------------------------------