-
Notifications
You must be signed in to change notification settings - Fork 65
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
PID not listening? #54
Comments
Just out of curiosity, have you tried with latest Rails version (or even lates 4.0.x series (4.0.13) |
When you run system() it blocks the current process so it cannot listen to rbtrace messages. Invoking rbtrace from the current process to connect back to itself doesn't make much sense and is not recommended. |
@tmm1 what would be the best recommendation based on my intention? |
You could execute it with: |
Hello! I have the following setup, using rails 4.0.6
require "rbtrace"
returnstrue
gem "rbtrace", require: false
And I still get the following error:
PID is defined and I'm running in a separate thread which I later then join to the main one, i.e:
Maybe I need to require rbtrace on the block passed to the new thread :) but if there's any known issues around requiring the library it would be good to know :)
I'm also using
puma
as my web serverThe text was updated successfully, but these errors were encountered: