KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q49381: CVP 2.30 Hangs When /O Is Specified, but Child Is Not Debugged

Article: Q49381
Product(s): See article
Version(s): 2.30
Operating System(s): OS/2
Keyword(s): ENDUSER | buglist2.30 | mspl13_basic
Last Modified: 27-OCT-1989

Beginning with protected-mode CodeView (CVP) Version 2.30, you can
debug child processes from within a parent process's CodeView session
by invoking CodeView with the /O switch. When the program is executed
to the point where the child process is invoked, CodeView displays a
prompt showing you the child's process ID (PID) and asks, "Do you wish
to debug (y/n)?". Entering "y" brings up the child process and allows
you to debug it. Pressing "n" should cause the child to execute
without any debugging.

Unfortunately, there is a problem in CVP 2.30 that causes CodeView to
hang if you answer no to debugging the child. The only workaround is
to always answer yes when prompted to debug a child process, or to
invoke CodeView without the /O switch because this prevents the prompt
entirely.

Microsoft has confirmed this to be a problem with CodeView Version
2.30. We are researching this problem and will post new information as
it becomes available.

If the program you are debugging is not a Presentation Manager (PM)
application, you may be able to kill the CodeView session if it should
hang as a result of answering "n" to the debugging child process. You
must switch to the Task Manager and use it to close the hung CodeView
session. If you are working on a PM application, the only workaround
may be to reboot the computer.

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.