-
Notifications
You must be signed in to change notification settings - Fork 36
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
Debugger terminates #87
Comments
Log file contents (I noticed the Vim plugin, 15:28:08: Executing :Rdebugger... |
Weird. Try to run this command from your logs just from console:
|
I got no output at all in the console. Maybe it's something with a hanging debugger (it keeps waiting at the end of log)? |
Hmm, you should get the PID after executing this command... |
Yes, I have tested following scenarios, both for ruby 1.9.3 and 2.0 and rails 4.0:
Both scenarios give me no pid. I launch vim using mvim -v command in the console. |
Hmm, and if you just run |
Yes, no problems at all. I also double checked my |
That sucks. :( The only thing I could recommend to do - debug rdebug-vim, which is part of 'debugger-xml' gem, and figure out why the PID is not printed as it should (here - https://github.com/astashov/debugger-xml/blob/master/lib/debugger/xml/extensions/vim_server.rb#L42) The problem is somewhere there, not inside vim-ruby-debugger itself. |
Aww :( I will try to debug that gem (and report if succeed). Thanks for help! |
No problem. :) Feel free to create the Pull Request there, if you find the source of the issue. |
Every time I run
:Rdebugger
I get messageCommand terminated
.Tested with ruby 2.0 and 1.9.3 and mvim 7.4.
Any ideas why it happens?
The text was updated successfully, but these errors were encountered: