ID Number: Q73303
3.50
OS/2
Summary:
When trying to debug multimodule programs under Microsoft CodeView
version 3.5, you must step or trace into a called module before
attempting to set a breakpoint in that module. If the called module
has not been stepped or traced into beforehand, CodeView will simply
beep when you attempt to set a breakpoint.
This information applies to the Microsoft CodeView Debugger version
3.5 for MS OS/2.
More Information:
To reproduce this problem, you can run any program that dynamically
calls another executable file (.EXE file).
Steps to Reproduce Problem
--------------------------
1. Under MS OS/2, start the Microsoft CodeView Debugger version 3.5
with the calling program, using the following command at the OS/2
command-line prompt:
CVP <name of driver program>
2. From the File menu, choose Open to open the called module:
ALT+F+O
A dialog box should appear, into which you can type the name
of the called routine, or you can use the file browser to locate
the called routine.
3. After positioning the cursor at the desired breakpoint location,
attempt to set a breakpoint by selecting Set Breakpoint from
the Watch menu:
ALT+W+S
4. Choose OK in the dialog box.
CodeView 3.5 will now issue a beep, rather than setting the desired
breakpoint.
To work around this problem, press F8 or F10 to step or trace from the
calling module into the called module, at which point you can set the
breakpoints normally.
Additional reference words: 3.50