PRB: Print Break in MFC App Running in Windows NT 3.51 CheckedLast reviewed: July 10, 1997Article ID: Q138993 |
2.00 2.10 2.20 4.00
WINDOWS NT
kbprint kberrmsg kbprb
The information in this article applies to:
SYMPTOMSWhile using the Visual C++ debugger, if you click Print or Print Preview in an MFC application running under Windows NT version 3.51 Checked Build, a message box appears: In the Visual C++ 2.x debugger, the message box contains:
Break caused by hard coded breakpoint instructionIn the Visual C++ 4.0 debugger, the message box contains:
User breakpoint called from code at 0x<8-digit address>The following message is also printed in the Output Window of the debugger:
BASE: GlobalFree called with a locked object. CAUSEMFC queries an HDEVNAMES handle for information about the printer device. This information is obtained by making calls to GlobalLock to get a valid pointer to the DEVNAMES structure. Under Win32, it is not technically necessary to call GlobalUnlock for every GlobalLock, so MFC doesn't always do so. The Checked Build of Windows NT 3.51 provides debugging information that warns you when GlobalFree is called on an object that does not have a lock count of 0. When this occurs, it outputs a trace message and causes a hard coded break instruction to be executed.
RESOLUTIONThe message and the break can be safely ignored. To continue with execution in the debugger, you can just click Go on the Debug menu, or press the F5 key.
STATUSThis behavior is by design.
|
Additional reference words: 2.00 2.10 2.20 4.00 3.00 3.10 3.20 4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |