Whether you have encountered the following troubles in your daily development work:
(1) When your application is running in a practical environment, the debugging information of the Trace Macro output cannot be seen because there is no VC debug environment.
(2) When your application is running in the actual environment, when the program exception has caused the application to crash, it cannot be positioned.
:) Now introduce you to Tool Software Tracer 3.0, which can replace the debug information output window in the VC environment, receive and display the TRACE information output from the DEBUG version of the VC environment, and your application does not need to Do any changes or join any modules.
:) For the Release version of the app, simply add the following code to the following code to TRACE debugging information to Tracer:
#ifndef _debug
Void Trace (LPCTSTSTST PSZFORMAT, ...)
{
Char BUF [512];
VA_LIST Arglist;
VA_Start (arglist, pszformat);
VSPrintf (buf, pszformat, arglist);
VA_END (arglist);
OutputDebugstring (buf);
}
#ENDIF
:) Tracer can support the debug information output of multiple applications at the same time, and the output of each application exclusive one window, which is especially suitable for C-S applications:) Tracer can filter the application's debug output information, so that you Run tracking focus on specific modules or specific functions:) Tracer can additional timestamp information before each debug information of the application output:) Tracer can save the application's debug output information for subsequent data analysis.
:) Whether it's a debug version or a Release version of the application runs in an actual environment. When an exception causes the application crashes, Tracer can make a big performance to quickly and accurately position the problem. As long as you record the address information when the application crashes (generally displayed in the crash information window of Windows popping) and supplied to the MAP file for the application, Tracer will accurately calculate the application's crash. Which module file that occurs in the source program, which function and the specific source code line.
:) Details can be
Www.microware.net.cn to see
