PRB: Debugee Exits When the Debugger Exits

 Last reviewed: February 26, 1997
Article ID: Q164205
3.1 3.5 3.51 4.00 WINDOWS NT kbprg kbprb

The information in this article applies to:

  • Microsoft Win32 Application Programming Interface (API) included with: - Microsoft Windows NT versions 3.10, 3.50, 3.51, 4.0 - Microsoft Windows 95

SYMPTOMS

When a debugger exits, the process being debugged (the "debugee") also exits.

STATUS

This behavior is by design.

MORE INFORMATION

There is no way to modify the configuration of the operating system to work around this behavior. There is no way to keep the debugee alive after the debugger exits.

In order to keep the debugee running, the debugger must remain running.

KBCategory: kbprg kbprb
KBSubcategory: BseDebug BseProcThrd
Additional reference words: 3.1 3.5 3.51 4.00 95 DebugActiveProcess
ContinueDebugEvent DebugBreak SetDebugErrorLevel WaitForDebugEvent
DEBUG_PROCESS DEBUG_ONLY_THIS_PROCESS
Keywords : BseDebug BseProcThrd kbprb kbprg
Version : 3.1 3.5 3.51 4.00
Platform : NT WINDOWS

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: February 26, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.