-
Notifications
You must be signed in to change notification settings - Fork 13
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
Debug macro makes function disappear inside an iprofile block #74
Comments
Sorry forgot to mention that I'm using Julia 0.3.11 on x86_64-linux-gnu. |
Indeed, it seems like a nasty interaction. As far as I can tell, the only thing that |
It's been so long since I've thought about IProfile, I don't remember much of anything about it. In these situations, |
There are a few other interactions with debug that I've wondered about along similiar lines. I notice issues when putting breakpoints in functions that are called through pmap or @parallel and so forth. I think the REPL breaks down with IO on separate threads. For similar reasons debug doesn't seem to work inside IJulia. As for Iprofile, I kind of like how it works. It's easier to understand for me. |
Yes, anyone who'd like to, please feel free to dig into this! I don't think I will be able to prioritize it myself. |
@mattcbro: That's a few issues in one message :) The IO trouble seems to be inherited from Julia's |
Consider the following code in badprofile.jl
Observe what happens if you try to use this code.
julia> require("badprofile")
julia> imgone()
ERROR: imgone not defined
julia>
Now suppose I remove the @debug macro from imgone. I then get the correct behavior
julia> require("badprofile")
julia> imgone()
I'm Here
There is some kind of nasty interaction between these macros in the two packages. Now it may be unreasonable to do debugging inside a profiling block, however one is supposed to be able to turn the profiler off without messing with the iprofile begin and end block.
Not sure if this is a debug problem or iprofile problem or both. This is not a show stopper by any means, but if it's intended behavior perhaps it should be documented or something.
The text was updated successfully, but these errors were encountered: