-
Notifications
You must be signed in to change notification settings - Fork 35
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
Code locations of iteration with break
are incorrect.
#485
Comments
I'd argue this is an issue with Base inserting the wrong line number node for this function (and probably iteration in general):
I don't think we can do anything about this here. |
Thank you. I'd keep this open until I open an issue upstream. |
simeonschaub
added a commit
to JuliaLang/julia
that referenced
this issue
Aug 10, 2021
Since lowering always inserts gotos and other instructions after loop bodies, this allows debuggers to give a more useful location for these instructions. fixes JuliaDebug/JuliaInterpreter.jl#485
vtjnash
pushed a commit
to JuliaLang/julia
that referenced
this issue
Aug 25, 2021
Since lowering always inserts gotos and other instructions after loop bodies, this allows debuggers to give a more useful location for these instructions. fixes JuliaDebug/JuliaInterpreter.jl#485
Closed by JuliaLang/julia#41857 |
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this issue
Feb 22, 2022
Since lowering always inserts gotos and other instructions after loop bodies, this allows debuggers to give a more useful location for these instructions. fixes JuliaDebug/JuliaInterpreter.jl#485
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this issue
Mar 8, 2022
Since lowering always inserts gotos and other instructions after loop bodies, this allows debuggers to give a more useful location for these instructions. fixes JuliaDebug/JuliaInterpreter.jl#485
Keno
pushed a commit
to JuliaLang/julia
that referenced
this issue
Jun 5, 2024
Since lowering always inserts gotos and other instructions after loop bodies, this allows debuggers to give a more useful location for these instructions. fixes JuliaDebug/JuliaInterpreter.jl#485
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found Debugger.jl points to a wrong code location in the following example:
This is because the current call frame misunderstand that the iteration comes from line 6, not line 3.
The text was updated successfully, but these errors were encountered: