Do you have a software recording system?
Maybe you are thinking about licensing one, or building your own? Use
this matrix as a guide to plan out whether it makes sense to use
ReplayDIRECTOR™ instead.
Check off the features that are supported by the recording
system you are considering:
| Record & Replay Features |
Replay DIRECTOR™ |
Other Systems |
| Always works 100% throughout the entire development cycle |
Yes |
|
Does not slow down performance and can be always be Recording,
even in production
|
Yes |
|
| Replays un-initialized stack & heap memory access bugs |
Yes |
|
| Replays multi-thread context switch timings, race conditions,
priority inversions and dead-locks |
Yes |
|
| Generates less than 1 MB of recording data per minute |
Yes |
|
| Memory addresses and pointers values are the same from Record to
Replay |
Yes |
|
| Can replay in the debugger with all symbols & debugging info,
set breakpoints and inspect data. |
Yes |
|
| Records all network data including asynchronous events and data |
Yes |
|
Records all file IO, including asynchronous operations
|
Yes |
|
| Records and Replays any 3rd party libraries your software may use |
Yes |
|
| Records interrupts, all callbacks, and delayed procedure calls
(DPCs) |
Yes |
|
Records low-level timers and assembly instructions like RDTSC and
MFTB
|
Yes |
|
We’ve spent several man years building a system that makes certain that
every line
of code executed during record will replay in the exact same way.
Other recording systems may not give you the features you'll need, and
the cost of building and maintaining your own recording system
throughout the life of your project may not be the best use of your time
and money.
Click Here to get in
touch with us! |
