-
Notifications
You must be signed in to change notification settings - Fork 9
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
Debugger sometimes repeating BREAKPOINT_SET events #61
Labels
Comments
From code it looks like this happen all the time when we put run to cursor breakpoint when other breakpoints are active in the same file. This spammy messages from debugger may confuse IDE, at least this happens in tests. We are failing before getting real answer about stopping at interested place. |
hurricup
added a commit
to Camelcade/Perl5-IDEA
that referenced
this issue
Mar 4, 2023
For some reason we are stopping process at some point before we got the answer. - more debug logging - replaced volatile boolean with atomic - replaced Thread.sleep with TimeoutUtil.sleep
hurricup
added a commit
to Camelcade/Perl5-IDEA
that referenced
this issue
Mar 4, 2023
For some reason we are stopping process at some point before we got the answer. - more debug logging - replaced volatile boolean with atomic - replaced Thread.sleep with TimeoutUtil.sleep
hurricup
added a commit
that referenced
this issue
Mar 5, 2023
By using this we may get additional output from debugger tests on CI
hurricup
added a commit
that referenced
this issue
Mar 5, 2023
We are removing request for breakpoint removal but keeping requests for set. This caused multiple BREAKPOINT_SET events sent to IDE each time we are setting breakpoint with other breakpoints in the file.
hurricup
added a commit
to Camelcade/Perl5-IDEA
that referenced
this issue
Mar 5, 2023
Trying to understand why run to cursor test is failing sometimes
hurricup
added a commit
to Camelcade/Perl5-IDEA
that referenced
this issue
Mar 5, 2023
See Camelcade/Devel-Camelcadedb#61 Trying to understand why run to cursor test is failing sometimes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See logs from failing run-to cursor test.
logs_1032.zip
The text was updated successfully, but these errors were encountered: