C++ Bug Validator provides automatic execution history logging of applications as they run. There is no need to recompile or relink your application. C++ Bug Validator works with debug information and/or MAP files. C++ Bug Validator allows you to perform execution history logging on your entire application, or on just the DLLs you require. You can also prevent files from being instrumented.
The execution history of your application is recorded line-by-line as each section of code corresponding to each source code line is executed. When working with multi-threaded applications, you can see the context switches between each thread. If you get a Bug of any kind, C++ Bug Validator will have a log of all the lines executed up until the point of the crash, not just the callstack for the crash.
This makes C++ Bug Validator an excellent tool for identifying otherwise hard to detect bugs and crashes. Combined with the companion software tool, C++ Bug Validator Client, you can identify the causes of crashes at customer sites without compromising your symbolic debugging information.
C++ Bug Validator has multiple displays to provide you with different perspectives onto the data you have collected.
Execution History
Detailed information about the program flow for the C++/VB application.
Diagnostic
Diagnostic information about the applicaton.
C++ Bug Validator runs on Windows Vista/XP/2000/NT.
C++ Bug Validator provides the following features:
Execution History
•Thread ID
•Module (DLL/EXE)
•Address
•Source code file and line number
•Function parameter values
•Function return values
•Local variable values
•Function name and offset from function start
•Coverage statistics updated as the application executes
•Ability to sort the data for display
•Ability to show execution history for one thread or all threads, showing thread context switches
•Colour coded display for at-a-glance detection thread context switching
•Source code display with line highlighting for examining source code in-situ
Data Views
•Execution history view. Shows execution history on a line by line basis
•Diagnostic messages. For detecting unforseen errors in the instrumentation. If things are not behaving as you expect, the answer may be here
Collect Crash Data at Customer Sites
•Use C++ Bug Validator to create KVI files to allow C++ Bug Validator Client to be used at customer sites without the need for PDB or MAP files. KVI files contained encoded filename and symbol information that cannot be decoded without KVK files (which you do not supply to the customer)
•Use C++ Bug Validator Client to collect data at customer sites without the customer being given PDB or MAP files containing debugging symbols
•Analyse data collected with C++ Bug Validtor Client using Bug Validator
•Protects your intellectual property by keeping your symbolic debugging information in your development labs, even whilst collecting data about crashes at remote sites
•Easy to use deployment wizard to create KVI files to send to your customer
Data searches
•Find function query
Startup
•Start by injecting into running process
•Start by launching a process and injecting into that process at startup
•Start by waiting for a process to start and injecting into that process at startup
Data export
•Execution History Data can be exported to HTML
•Execution History Data can be exported to XML
Instrumentation
•Instrumentation is fast, a few seconds, not tens of minutes
•Runs at nearly full speed of non-instrumented application, not 2 or 10 times slower
No need to rebuild
•No need to rebuild or relink your application. Simply requires PDB and/or MAP files for each module (DLL/EXE) in the application
Compatibility
•Works with the following compilers:
•Microsoft Visual Studio 2015, 2013, 2012, 2010, 2008, 2005, .net 2003, .net 2002, 6.0
•Microsoft Visual C++
•Microsoft Visual Basic 6
•Intel Performance C++ compiler
Very configurable, almost all options are configurable by the user. Includes an option to reset to the default settings
Operating Systems
•Microsoft Windows 10 64 (32 bit applications only)
•Microsoft Windows 8 64 (32 bit applications only)
•Microsoft Windows 7 64 (32 bit applications only)
•Microsoft Windows Vista 64 (32 bit applications only)
•Microsoft Windows XP 64 (32 bit applications only)
•Microsoft Windows 10
•Microsoft Windows 8
•Microsoft Windows 7
•Microsoft Windows Vista
•Microsoft Windows Server 2012
•Microsoft Windows Server 2008
•Microsoft Windows Server 2003
•Microsoft Windows XP