-
Notifications
You must be signed in to change notification settings - Fork 43
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
Different behavior in debugger #275
Closed
Comments
This seems to be the same issue as JuliaDebug/JuliaInterpreter.jl#415. |
timholy
added a commit
to JuliaDebug/JuliaInterpreter.jl
that referenced
this issue
Dec 16, 2020
This supports SSAValue args for cglobal while also fixing a bug in which a GotoIfNot ended up going to the wrong statement. The latter was a consequence of incorrect :call unnesting. Fixes #455 Fixes #454 Fixes #415 Fixes JuliaDebug/Debugger.jl#275 Improves #354
timholy
added a commit
to JuliaDebug/JuliaInterpreter.jl
that referenced
this issue
Dec 17, 2020
This supports SSAValue args for cglobal while also fixing a bug in which a GotoIfNot ended up going to the wrong statement. The latter was a consequence of incorrect :call unnesting. Fixes #455 Fixes #454 Fixes #415 Fixes JuliaDebug/Debugger.jl#275 Improves #354
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the debugger to call Python via PyCall the return type can be different than when not using the debugger. Here's an MWE where @run gives a different return type:
Using Python 3.7.4 and numpy 1.16.5.
The text was updated successfully, but these errors were encountered: