-
Notifications
You must be signed in to change notification settings - Fork 130
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
remote debugger failing on first hit with puma #1121
Comments
You mean that the "fail" is showing the "# No sourcefile available for /usr/local/bundle/gems/puma-6.4.2/lib/puma/single.rb I'm not sure but |
I figured out that in order to make thing work is
However, this sequence fails
|
Alrighty! Here's an even more minimal proof of concept, without Rails, ActiveSupport, etc. Running it is trivial, and the instructions are in the readme. I was able to upgrade Puma to 6.6.0 (latest) and still trigger the bug. However switching to |
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: