0 items - $0.00

'How did I get here from there?' for software.

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 Bug Validator to create KVI files to allow 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 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 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
  • Bug Validator Client is free. You do not need to purchase Bug Validator Client to use it at your customer sites (unlike competing products). You only need to purchase Bug Validator

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 2019, 2017, 2015, 2013, 2012, 2010, 2008, 2005, .net 2003, .net 2002, 6.0
    • Microsoft Visual C++
    • Microsoft Visual Basic 6
    • 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

  • 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

If you need support for older Windows operating systems (for example you may be using Windows 2000 Embedded) we can provide special builds for these operating systems. Please contact us for details.

  • Microsoft Windows 2000
  • Microsoft Windows NT 4

Go to Top ^^


Information