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
Describe the bug
When hitting breakpoint via placing "debugger" into source code, and connecting with remote debugger, with sinatra controller and puma web server in local docker container, first time when "debugger" is hit will fail, as described below
For example,
Puma started freshly serving sinatra app in local docker container
33| def some_method_called_via_puma_via_sinatra_controller
=> 34| debugger
35| some logic...
37| end
38|
(rdbg:remote) n
# No sourcefile available for /usr/local/bundle/gems/puma-6.4.2/lib/puma/single.rb
Stop by SIGURG
(rdbg:remote) n
# it looks like it tries to step in code, but in reality context is lost
(rdbg:remote) n
[1, 7] in $(Gem)/rack-2.2.9/lib/rack/file.rb
1| # frozen_string_literal: true
2|
3| require_relative 'files'
4|
=> 5| module Rack
6| File = Files
7| end
(rdbg:remote) c
Thus only way to end to proceed is to hit "continue", since control flow has jumped into some odd place, and now, after this failure when doing same request again, debugger works as espected (i.e. does not hit this "SIGURG" which seems to break thing).
Makes usage rather irritating since after every modify of code (and restart of web server thus), have to first hit debugger "cold", and failing, and hitting continue, and now it seems to be "hot", and can actually succeed.
To Reproduce
Local docker container
running sinatra app with puma on it
setting up remote debugger
adding breakpoint via placing "debugger" into code
launching app on container
performing some request hitting "debugger" put in code
connect remote debugger to process
=> fails on first time, if hitting continue, and retrying request it works as expected
Expected behavior
It would not fail on first time, since it makes debugging few cases difficult.
Additional context
Issue has been there for a while, i.e. it has had this failure always for me with this debug gem
The text was updated successfully, but these errors were encountered:
Your environment
ruby -v
: 3.3.5rdbg -v
: 1.9.2Describe the bug
When hitting breakpoint via placing "debugger" into source code, and connecting with remote debugger, with sinatra controller and puma web server in local docker container, first time when "debugger" is hit will fail, as described below
For example,
Puma started freshly serving sinatra app in local docker container
Thus only way to end to proceed is to hit "continue", since control flow has jumped into some odd place, and now, after this failure when doing same request again, debugger works as espected (i.e. does not hit this "SIGURG" which seems to break thing).
Makes usage rather irritating since after every modify of code (and restart of web server thus), have to first hit debugger "cold", and failing, and hitting continue, and now it seems to be "hot", and can actually succeed.
To Reproduce
=> fails on first time, if hitting continue, and retrying request it works as expected
Expected behavior
It would not fail on first time, since it makes debugging few cases difficult.
Additional context
Issue has been there for a while, i.e. it has had this failure always for me with this debug gem
The text was updated successfully, but these errors were encountered: