PRB: CodeView May Appear to Hang on gets() If Screen Swap Is Off (62663)
The information in this article applies to:
- Microsoft CodeView for MS-DOS 3.0
- Microsoft CodeView for MS-DOS 3.11
- Microsoft CodeView for MS-DOS 3.14
- Microsoft CodeView for MS-DOS 4.0
- Microsoft CodeView for MS-DOS 4.01
- Microsoft CodeView for MS-DOS 4.05
- Microsoft CodeView for MS-DOS 4.1
- Microsoft CodeView for OS/2 3.0
- Microsoft CodeView for OS/2 3.11
- Microsoft CodeView for OS/2 3.12
- Microsoft CodeView for OS/2 3.5
This article was previously published under Q62663 SYMPTOMS
The Microsoft CodeView Debugger will appear to hang when you step or
execute past a call to the gets() run-time routine if the Screen Swap
option is turned off.
CAUSE
The apparent lock-up results because the gets() call causes focus to
shift to the debuggee's screen and there is no way for CodeView to get
to that screen with Screen Swap off.
Since in MS-DOS, the debuggee's screen still displays CodeView, you
may be able to type in the information and press Return to continue.
This will temporarily display the debuggee's input over CodeView's
screen. A better method in MS-DOS is to break execution with CTRL+C so
that you may turn swapping back on.
RESOLUTION
To get past this deadlock with CVP under OS/2, manually switch screen
groups to the one labeled "CVP app appname.EXE". Once there, you can
provide a response to the waiting gets() call. After entering a
string, you can switch back to the screen group running CVP and
continue debugging.
Modification Type: | Major | Last Reviewed: | 10/23/2003 |
---|
Keywords: | kb16bitonly KB62663 |
---|
|