TracePlus Win32
|
TracePlus/Win32 allows you to monitor and analyze the interaction between your Win32 software and multiple Win32 APIs. Supported APIs that are displayed in realtime include ODBC, OLE, COM, TAPI, WININET, registry, DB-Library, and more. The integrated SQL capture window displays SQL statements generated by the supported database APIs and the status window displays DLL version information, OutputDebugString() calls, and more.
TracePlus/Win32 Features:
* Supported API functions that fail are indicated in the Diagnostics View along with the Win32 error code describing the failure
* Displays API calls originating from ActiveX controls and COM objects instanced by an application
* Displays API and ODBC calls originating from a child process
* Displays ODBC calls originating from the Microsoft Jet Database Engine, and Active Data Objects (ADO)
* Works with most commercial Win32 applications (release versions) with no modifications to the target software
* Compatible with Microsoft Terminal Server and Remote Desktop ( Windows 2000, Windows 2003 Server)
* Supports Win32 .EXE files from all languages and compilers (including Visual C++, Visual Basic, Visual C#, Microsoft Access, MASM, Borland Delphi and C++ Builder, Sybase PowerBuilder)
* Works with most Win32 Services on platforms that support services (Windows 2000, Windows XP, Windows 2003 Server)
* The Registry View displays accesses made to the Windows registry by one or more processes. Using a unique algorithm, TracePlus determines the full key name as well as displaying the value of the key.
* Registry accesses that fail are indicated in the Registry View along with the Win32 error code describing the failure
* User-definable filters limit what is displayed in the Registry View to the types of Registry accesses that interest you
* The text of SQL statements transmitted via the ODBC API is displayed in the SQL View
* Contents of result columns displayed in the SQL View along with the SQL statement
* Displays the contents of all variables bound to parameters in a SQL Statement. This information is displayed inside the ODBC functions SQLExecute() or SQLExecDirect() in the Diagnostics View.
* Execution time is profiled in the SQL View for each SQL statement
* SQL statements that fail are indicated in the SQL View along with full ODBC error information describing the failure
* File opening, closing, creation, deletion, copying, moving, and renaming by an software are detailed in the File I/O View
* File reads, writes, locks, and unlocks are detailed in the File I/O View
* Manipulation of mapped files (open, create, close, read, write, flush) are detailed in the File I/O View
* The referenced filename is displayed for every file open or create appearing in the File I/O View
* Mapped Views are supported in the File I/O View
* User-definable filters limit what is displayed in the File I/O View to the types of File I/O that interest you
* The status of COM object creation via CoCreateInstance() and CoCreateInstanceEx() is detailed in Status View
* DLL loading and unloading is profiled in the Status View. DLL load events contain version information (if available) for the module being loaded.
* The text of messages sent via OutputDebugString() appears in the Status View
* User definable filter profiles enable separate API configurations for different capture sessions
The license of this software is Free Trial Software, the price is $199.95, you can free download and get a free trial.

