Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!mms00786
From: mms00786@uxa.cso.uiuc.edu
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: MSC 6.0 Bug/struct params
Message-ID: <139400008@uxa.cso.uiuc.edu>
Date: 19 Jul 90 02:12:00 GMT
References: <139400007@uxa.cso.uiuc.edu>
Lines: 28
Nf-ID: #R:uxa.cso.uiuc.edu:139400007:uxa.cso.uiuc.edu:139400008:000:1041
Nf-From: uxa.cso.uiuc.edu!mms00786    Jul 18 21:12:00 1990


Not to harp on Codeview, but I too experience a 'sticking' control key when I
quit Codeview session, assuming my session did not lead to a 3 finger salute.
Solution : hit the control key. Another, more serious bug :

The code :
                      case 1 :
                           bBoolean = true;
                           ...
                           ...
                           break;

                      case 2 :
                           bBoolean = true;
                            /* different code here */
                           break;

So, I set a breakpoint at the first bBoolean = true statement under case 1.
Breakpoint is correctly met. I hit f8 (step) or f10 (step, not trace), and
the code executed is the code immediately after bBoolean = true under
case 2!! For a moment, I thought there was some silly flaw in the MSC 6.0
code generation. I produced a listing file, and found that this was not
the case. Solution : do not set bp at bBoolean = true;.

I do have a AMI bios, so maybe that's it. 

Milan
.