FIX: Visual Workbench Cannot Find WndProc in Windows 3.1 Apps (116167)
The information in this article applies to:
- The Visual Workbench Integrated Debugger, when used with:
This article was previously published under Q116167 SYMPTOMS
The Visual Workbench debugger allows you to set a breakpoint in a window
procedure. This makes it possible for the application being debugged to
break in the function when a specific message or class of messages is
received. If the Windows version 3.1 prototype is used for the window
procedure, the Visual Workbench is not able to identify the function as a
window procedure. As a result, the WndProc list box in the Breakpoints
dialog box that lists the available window procedures does not list the
function.
CAUSE
The Visual Workbench uses the Windows version 3.0 WndProc prototype, which
reads as follows:
long _far _pascal WndProc(WORD, WORD, WORD, LONG)
The Windows version 3.1 WndProc prototype is slightly different:
long _far _pascal WndProc(HWND, UINT, WPARAM, LPARAM)
When the Windows version 3.1 prototype is used, the Visual Workbench is not
able to find the WndProc function.
RESOLUTION
Even though it is not possible to select the window procedure to break in
from the WndProc list box in the Breakpoints dialog box, it is possible to
manually enter the name of the function.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products
listed at the beginning of this article. This problem was corrected
in Visual C++ version 2.0.
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | kbBug kbDebug kbfix kbide KB116167 |
---|
|