-
Notifications
You must be signed in to change notification settings - Fork 90
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
Why I cannot debug a code in async block in intellij #136
Comments
Yes I have the same problem, but It doesn't happen every time. |
I noticed this. Annoying as hell. Actually this is probably number 1 on my priority list. This and error handling. |
Yes. Its very annoying. We used Play framework and everything is written within async block. It happens always for me. |
I see that the IntelliJ Scala Plugin team has just added some support for scala-async to the debugger. JetBrains/intellij-scala@64774de The bug report, SCL-9039, seems the be reporting the same problem you're discussing here. As a nice bonus, @niktrop seems to have added special support in "evaluate expression" so that local variables in the user-written code are retrieved from the corresponidng name-mangled fields of the state machine class. Thanks! @niktrop Let me know if there is anything we can do in the macro to make your life easier here.. @lahirug @efiko12 @pkolaczk @worldofprasanna Thanks for your patience with this problem. Could I ask you to test out the latest nightly of the Scala Plugin (this requires use of IDEA 15) and report whether the situation is improved? |
There are some problems with availability of local variables and fields. Try this example:
Field, generated for f2 is already null. And local variable f1 is not visible from the breakpoint location. I suppose wrong debug info for local variable table is generated. |
With the recent plugin I can put a breakpoint inside of async block and now it properly stops there. However, I noticed I can't step over await calls. Much better than before, but still needs more work. |
Anybody noticed this and found a workaround ?
The text was updated successfully, but these errors were encountered: