-
Notifications
You must be signed in to change notification settings - Fork 36
(breakpoint mode) compile the code behind breakpoint #298
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
Comments
Breakpoints needs to be addable, removable, modifiable while the code is running, otherwise you could just insert some hook directly into the source code Please see #204 for some more discussion about different approaches to improving performance. |
@KristofferC Well, that is exactly what I want. Just to check the values of the variables inside workspace (especially if the code is inside a function). |
A feature could be added to Debugger.jl / Juno debugger that allows you to insert some macro and gives you an interactive thing with the local variables (using |
As I said, ideally, after checking the values of the variables, if users press continues, the debugger should scan the rest of the code to see if there are new breakpoints there. Isn't it possible to compile part of the code and call the interpreter/debugger after that? |
Feel free to give #297 (comment) a go, we might get around to adding that to Debugger.jl/Juno at some point. |
@pfitzseb Thank you! should I create an issue there? or you can move this to that repository? |
I am not how practical this is or if it is done already
To speed up the debugging, is it possible to compile the code before the breakpoint specified by line number? and if the breakpoint is inside a control flow (such as if, while, for, etc.) the compilation should be done until before the control loop.
I am assuming to achieve this, a new debugger mode which is only meant for hitting the breakpoints is needed.
The text was updated successfully, but these errors were encountered: