The Chronon Time Travelling Debugger allows you to playback Chronon recordings of your Java programs and easily find root cause of defects. It is specifically built from the ground up to allow debugging of long running programs that run for days/months and are highly multithreaded. The debugger plugs seamlessly into Eclipse adapting itself naturally to your workflow. You can also use the Eclipse integration of the Chronon Debugger to easily record programs on your development machines from within Eclipse.Overview Features Post Execution Logging Pricing Download
Chronon allows you to step not only forward, but also backward in your program’s execution. The Step Backward functionality is critical to understanding what was it that led to say, throwing of an exception, in your program’s execution.
Chronon is not like your traditional debugger. We designed it from the ground up to allow easy debugging of complex, highly multithreaded programs.
The groundbreaking Post Execution Logging feature allows you to add logging to any piece of code *after* it has run and see the results instantly. This means you can get rid of log files and the pesky log statements cluttering your code.
We’ve integrated with the top free IDE in the world. Chronon integrates seamlessly with Eclipse. No need to learn a whole new environment. You can literally become a master of Chronon in minutes and start debugging immediately.
Have a recording that is 50 hours long? You don’t need to wait another 50 hours to see what happens towards the end. The Chronon Time Travelling Debugger allows you to jump instantly to any point in the execution of your program, making it extremely easy to debug long running programs. You can instantly see the entire state of your program, all the threads, variables, etc when you jump to any point in time.
Needed by each developer to playback the recordings and find root cause.Find out how
No need to clutter your code with logging statements.
You no longer have to think about whether to add logging to a piece of code or not.
Your program doesn’t have any overhead of logging code anymore.
Now you can easily add logging anywhere at all in your code and see the results exactly as if the log statement was there if you had put it in your original code.
Yes, you can add logging after your program’s execution!
See the results of the ‘post execution log statements’ instantly inside Chronon exactly as if they were present had you put them in your code. You don’t have to wait for your program to run for hours again to see the results. Its instant!
Click on any of the resulting log msgs to jump instantly to the point in time of log execution and see all state and step back to find root cause of issue.
You can add and see the values of all the variables and the state of your program in your ‘post execution’ logging statements.
Yes, you can actually step *back*! The Chronon Debugger allows you to step not only forward, but also backward in time, allowing you to easily find out what was it that caused an issue.
Instantly see all the exceptions thrown in your program. Click on an exception to jump instantly to when it was thrown and examine all the state. You can step back from that point on, to see what caused that exception to be thrown in the first place.
Click on a variable in Chronon and see all the values ever assigned to it. Clicking on a value takes you instantly to the point in time when that value was assigned. Extremely handy for finding things like why a variable became null.
Chronon offers a wide range of ultra-rich filters to narrow down your bug hunt and get you to exactly what you are looking for. The filtering capability in Chronon is far beyond what conditional breakpoints in traditional debuggers offer.
The groundbreaking Post Execution Logging feature allows you to add logging anywhere, to any piece of code after it has run and see the results instantly. This means you can get rid of log files and the pesky log statements cluttering your code.
The Chronon Debugger does away with the old, broken mechanism of breakpoints. With Chronon you just jump directly to where you want to examine your code, instead of placing and managing breakpoints.
Step into a method call and instantly see the execution path taken by it. Execution path is not the same as code coverage. The Execution path in Chronon shows you a separate execution path for each different call to a method. Thus a million different calls to the same method would result in a million different execution paths.
Method History shows you instantly, all the calls made to a method. At a glance you can see which thread the method was called on, its return value and arguments. Click on a call to jump directly to it.
Time bookmarks are, as the name suggests, bookmarks in ‘time’. Place them wherever you find something of interest while debugging and you can return to that point in time anytime later.