PRB: Debugging the Open Common Dialog Box in WinDbg

 Last reviewed: November 2, 1995
Article ID: Q99952
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK), versions 3.1, 3.5, 3.51, and 4.0

SYMPTOMS

When debugging an application that uses the Open common dialog box (created by the GetOpenFileName() function) in WinDbg, the program stops and the following information is displayed in the Command window: 

   Thread Terminate: Process=0, Thread=2, Exit Code=1

CAUSE

The Open common dialog box causes a thread to be created. At this point in the debugging, that thread has terminated. By default, WinDbg halts whenever a thread terminates.

RESOLUTION

Execute the go command (type "g" at the command prompt). Execution will continue.

MORE INFORMATION

To prevent WinDbg from halting when a thread is terminated, select Debug from the Options menu and check "Go on thread terminate."

Additional reference words: 3.10 3.50 4.00 95
KBCategory: kbtool kbprb
KBSubcategory: TlsWindbg

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 2, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.