-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naive_interpreter : Adding object inspector #2696
Open
Delja
wants to merge
7
commits into
nitlang:master
Choose a base branch
from
Delja:stream
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🤖 ok to test |
Delja
force-pushed
the
stream
branch
9 times, most recently
from
May 24, 2018 16:03
088c2b1
to
0c82c50
Compare
privat
requested changes
May 28, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- move most stuff into a submodule of native_interpreter (that you can
intrude import
) - simplify the frame management that is very complicated
- use command names of gdb. eg.
next
step
continue
andfinish
This method is catch by the interpreter to display the object value and to start the step-by-step execution. This method MUST not be used by programs, it is here for debugging in the interpreter Signed-off-by: Florian Deljarry <[email protected]>
Add : - Class ObjectInspected to represent the inspected object - Class ObjectInspector to provide the inspect_object method that will return the inspect object as a tree (OrderedTree[ObjectInspected]) Signed-off-by: Florian Deljarry <[email protected]>
Add : -The step-by-step execution in naive_interpreter -Print the inspected object Signed-off-by: Florian Deljarry <[email protected]>
Signed-off-by: Florian Deljarry <[email protected]>
Add: -'backtrace full' option to print the local variables of the method -'watch' option to print all selected values with 'object_id' -'continue' option to execute the code until the next break point 'object_id' Signed-off-by: Florian Deljarry <[email protected]>
Add: - Reading null variables and instances - Using step interpreter to interpretation Signed-off-by: Florian Deljarry <[email protected]>
Delja
force-pushed
the
stream
branch
2 times, most recently
from
June 12, 2018 19:34
9b04ba9
to
9d490aa
Compare
Adding the Possibility to add and remove breakpoint during the interpretationNew breakpoint future Signed-off-by: Florian Deljarry <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add an object inspector to the naive interpreter.
To use it, you call the .inspect_o method on the object you want to inspect. The interpreter will then display the object as a tree. Note that the call to .inspect_o is considered as a breakpoint and will stop the interpreter from running to enter on step-by-step mode. To define some breakpoints on start interpretation you can use the command –break, to add breakpoint enter ‘break [file name] [line numbers]’ to remove breakpoint enter ‘clear [file name] [line numbers]’.
The step-by-step mode offers different features:
If you enter anything else you will leave the step-by-step mode