Important Notice
The pages on this site contain documentation for very old MS-DOS software,
purely for historical purposes.
If you're looking for up-to-date documentation, particularly for programming,
you should not rely on the information found here, as it will be woefully
out of date.
Windows Breakpoint Message (WBM)
◄Up► ◄Contents► ◄Index► ◄Back►
────────────────────────────────────────────────────────────────────────────
Command: Windows Breakpoint Message (WBM)
Syntax: WBM [winproc] [msgname | msgclasses]
Summary: Sets a breakpoint on a Windows message or a class of
Windows messages.
Arguments:
<winproc> The symbol name or address of an application's window
function.
<msgname> The name of a Windows message, such as WM_PAINT.
<msgclass> A string of the following characters that identifies
one or more classes of messages.
Message Class Type of Windows Message
m Mouse
w Window management
n Input
s System
i Initialization
c Clipboard
d DDE
z Nonclient
Description:
In CVW, you can set a breakpoint on a Windows message or a class
of Windows messages. This lets you track your application's
response to user input and window-management messages.
Once you have set a Windows breakpoint, it appears in the list of
breakpoints and may be enabled, disabled, and cleared with the
usual CodeView breakpoint commands.
See: ◄Breakpoint Clear (BC) Command►
◄Breakpoint Disable (BD) Command►
◄Breakpoint Enable (BE) Command►
◄Breakpoint List (BL) Command►
Example:
If your application is failing to refresh its window, you might
set a breakpoint on the WM_PAINT message so that you can watch
your program's behavior. The following command halts execution
whenever the application's MainWndProc function receives a
WM_PAINT message:
WBM MainWndProc WM_PAINT
-♦-