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
I'm trying to debug a separate issue, where it seems the WebConsole thread is hanging instead of reporting an error. When I connect to the puma server with rdbg -A, do th to list the threads, then th 13 (or whatever to pick the stuck thread), then do bt, I get a big exception printed to the puma output:
Also, when this happens, the console input for rdbg doesn't return. I have to hit ^C, and it prints "Stop by SIGURG", and I'm able to input commands again.
To Reproduce
Have a stuck thread using 100% CPU (I'm not sure that that's a requirement, its what I'm investigating).
Connect rdbg to the process, and switch to the stuck thread.
Print the backtrace for that thread.
Expected behavior
Successfully print the backtrace for a frame with nil for block_loc, or determine why a frame would have that.
Additional context
It looks like its coming from thread_client.rb:85, so I printed out the values for level, block_loc, args and frame:
I'm able to get it to not blow up by changing the code like this:
- "#{colorize_blue("block")}#{args_str} in #{colorize_blue(block_loc + level)}"+ "#{colorize_blue('block')}#{args_str} in #{colorize_blue([block_loc, level].compact.join)}"
But, I'm not sure why block_loc is nil (and level is empty string), and if that indicates a larger problem.
The text was updated successfully, but these errors were encountered:
Your environment
ruby -v
: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [x86_64-linux]rdbg -v
: rdbg 1.10.0Describe the bug
I'm trying to debug a separate issue, where it seems the WebConsole thread is hanging instead of reporting an error. When I connect to the puma server with
rdbg -A
, doth
to list the threads, thenth 13
(or whatever to pick the stuck thread), then dobt
, I get a big exception printed to the puma output:(formatted for readability, such as it is)
Also, when this happens, the console input for rdbg doesn't return. I have to hit
^C
, and it prints "Stop by SIGURG", and I'm able to input commands again.To Reproduce
Expected behavior
Successfully print the backtrace for a frame with
nil
forblock_loc
, or determine why a frame would have that.Additional context
It looks like its coming from thread_client.rb:85, so I printed out the values for
level
,block_loc
,args
andframe
:I'm able to get it to not blow up by changing the code like this:
But, I'm not sure why
block_loc
is nil (andlevel
is empty string), and if that indicates a larger problem.The text was updated successfully, but these errors were encountered: