Loading Profile...
Twitter, 
Facebook, or email.
Jump to the next execution point in the current thread.
How to jump to next nearest recorded execution path in eclipse. Step forward seems just to jump to the next execution point in the current method, but I need to jump to the next executed code whenever it is in the method or not.
Official Responses
-
EMPLOYEE
I’m happy
Misha,
I understand that given the information we record, we definitely could take you to the next recorded method in your code once you reach a point where you enter unrecorded/3rd party code.
We currently don't have the feature implemented, but what we do have is comparable to what you would get debugging with a standard debugger.
I will change the 'type' of the thread from 'question' to 'idea' so this remains on our radar as a feature to implement and others can vote and add suggestions for this feature. -
Well, think of a regular debugger.
In a regular debugger, you can't just jump to the 'next' execution point of interest either. You just keep stepping and you land into third party code.
So in a regular debugger you place a breakpoint at a point of interest in your code and let it run till that point is hit.
Same goes for Chronon, only instead of setting a breakpoint and waiting, you just jump directly to the line/method of interest.
Please look at this link to understand the differences more clearly:
-
Well, think of a regular debugger.
In a regular debugger, you can't just jump to the 'next' execution point of interest either. You just keep stepping and you land into third party code.
So in a regular debugger you place a breakpoint at a point of interest in your code and let it run till that point is hit.
Same goes for Chronon, only instead of setting a breakpoint and waiting, you just jump directly to the line/method of interest.
Please look at this link to understand the differences more clearly:
Comment -
-
I have read that link, it is good when you know the necessary method. Unfortunately that is not my case.
Using debugger I can step through code and find out what code would be called. But in chronon I have only recorded part of the entire execution path and sometimes that is not so easy to guess what code would be called next, especially when you are new to the code.
Why are you liking so tight to the traditional debugger? Chronon is much better as it facilitates time travelling, so why not to allow to select specific time to jump to?
That would be nice asking chronon questions like that: what code will be executed right after this line. Event more: chronon's feature of filtering code on recordable and non-recordable makes it easier to follow relevant program's path. -
-
>so why not to allow to select specific time to jump to
How would you know the time value in advance to jump to? ;-)
A program can have a 100 million time events, you dont know which one to jump to in advance
>I can step through code and find out what code would be called
In my experience, almost all the time when the code enters 3rd party, there is so much going on there that you don't want to and most times cant step through it to get back to where your code is called back. -
-
> How would you know the time value in advance to jump to? ;-)
>A program can have a 100 million time events, you dont know which one to jump to in advance
that is the nearest recorded command in the future
> In my experience, almost all the time when the code enters 3rd party, there is so much going on there that you don't want to and most times cant step through it to get back to where your code is called back.
using chronon I could do it, as it filters third party code and my own code, so jumping to the nearest recorded command will show me what my code will be called. Life becomes easier. -
-
EMPLOYEE
I’m happy
Misha,
I understand that given the information we record, we definitely could take you to the next recorded method in your code once you reach a point where you enter unrecorded/3rd party code.
We currently don't have the feature implemented, but what we do have is comparable to what you would get debugging with a standard debugger.
I will change the 'type' of the thread from 'question' to 'idea' so this remains on our radar as a feature to implement and others can vote and add suggestions for this feature. -
-
-
-
> We currently don't have the feature implemented, but what we do have is
> comparable to what you would get debugging with a standard debugger.
yes, but you strive to provide something that is far more versatile than a standard debugger :-) -
-
1I'd like to throw some support behind this as well. In fact I think it could probably be a major feature.
Why? Well, in my particular case I have a huge legacy project I'm dealing with that is full of spaghetti code and all sorts of fun anomalies. One of the side effects is that I hardly know where my code is going or what it is doing.
Now, if there's a specific bug that has been hit, that's great, and the tool works fine as is.
But, what I keep wishing is that I could simply step through our code to see what happens when a button is pushed. Call it "exploratory debugging" if you will. I think it would make it easier for people working on (poorly documented) legacy code to get a grip on exactly what their system is doing so they can more readily make systematic changes. -
