bug validator feature list

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 Crash Validator to create KVI files to allow Crash 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 Crash Validator Client to collect data at customer sites without the customer being given PDB or MAP files containing debugging symbols
Analyse data collected with Crash Validtor Client using Crash 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
Crash Validator Client is free. You do not need to purchase Crash Validator Client to use it at your customer sites (unlike competing products). You only need to purchase Crash Validator

Data searches

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

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 6.0, 7.0, 7.1, 8.0, 9.0 .net (2002, 2003, 2005, 2008)
- Microsoft Visual Basic
- Intel Performance C++ compiler
- Contact us if your compiler is not listed

Miscellaneous

Very configurable, almost all options are configurable by the user. Includes an option to reset to the default settings

Operating Systems