The information in this article applies to:
SYMPTOMSWhile debugging a Visual C++ application, if TRACE statements are sent to the output window consecutively in quick succession, the IDE tends to skip some statements. CAUSEWhen TRACE statements are sent in quick succession, the IDE buffers the strings. It tries to keep the screen output current, so in the event of too many calls to OutputDebugString to accomplish that, some lines are skipped. RESOLUTIONCurrently, there is no workaround to this problem. _RPT() and the SDK sample DBMON, which is a similar utility, could be used if all the consecutive TRACE statements need to be captured in the output window, while debugging. STATUSThis behavior is by design. MORE INFORMATIONThis scenario can be easily reproduced using a combination of TRACE statements as shown below:
When trying to debug an application with the above code, the output window will resemble the following code snippet:
The output window does not consistently show the same pattern when skipping TRACE statements; rather, it shows different patterns depending on machine speed and number of iterations.
REFERENCES(c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Vidyanand N. Rajpathak, Microsoft Corporation. Additional query words:
Keywords : kbCRT kbDebug kbWinOS2000 kbVC500 kbVC600 kbDSupport |
Last Reviewed: January 17, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |