You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doesn't seem to work well with multithreaded debugger statements. The program does not print out expected local variables and seems to hang forever after last continue statement.
The first time I reach a breakpoint it shows me in the hello = "hello" block. When I type out hello though it than jumps me to hello = "world" block. After typing out hello a second time, it prints out the string "hello" instead of "world". If I type continue it hangs forever after that. If I run the program without the debugger statements it doesn't hang.
Expected behavior
I would expect debugger to be somewhat threadsafe. Obviously debugger cannot necessarily control the order of these two debuggers. The second debug statement may execute first but I'd expect that the breakpoint would match the local variable and I'd expect typing continue would than make the program keep running and go to the next debugger statement or terminate the program if no more debugger statements.
The text was updated successfully, but these errors were encountered:
Thank you. This code is great to reproduce the issue.
Honestly speaking current thread management is not strict and this is a time to consider strict management...
I can't continue after hitting a breakpoint with Puma and I believe this might be the same issue. Just curious.. Is it a known issue that debug can't be used with puma due to this? Or am I doing something else wrong? (I've tried and failed on several rails projects. Changing to webrick makes it work)
Your environment
ruby -v
: 3.2.2rdbg -v
: 1.8.0Describe the bug
Doesn't seem to work well with multithreaded debugger statements. The program does not print out expected local variables and seems to hang forever after last continue statement.
To Reproduce
Given the following ruby code:
The first time I reach a breakpoint it shows me in the
hello = "hello"
block. When I type outhello
though it than jumps me tohello = "world"
block. After typing outhello
a second time, it prints out the string "hello" instead of "world". If I typecontinue
it hangs forever after that. If I run the program without the debugger statements it doesn't hang.Expected behavior
I would expect
debugger
to be somewhat threadsafe. Obviously debugger cannot necessarily control the order of these two debuggers. The second debug statement may execute first but I'd expect that the breakpoint would match the local variable and I'd expect typingcontinue
would than make the program keep running and go to the next debugger statement or terminate the program if no more debugger statements.The text was updated successfully, but these errors were encountered: