allow clients to connect over unix domain sockets#166
Closed
tdyas-stripe wants to merge 1 commit intoruby-debug:masterfrom
Closed
allow clients to connect over unix domain sockets#166tdyas-stripe wants to merge 1 commit intoruby-debug:masterfrom
tdyas-stripe wants to merge 1 commit intoruby-debug:masterfrom
Conversation
Author
|
Looks like CI builds failed for Ruby v1.8.7 and v1.9.3. Any suggestions on how to modify the API to work on those earlier versions? |
Merged
Contributor
|
This should be closed in favor of #183. |
|
To connect client using a port I used this configuration shown below: Launch.json rdebug-ide started with the following command: If I use unix socket instead of port, how do I connect my client to the unix socket? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow debugger clients to connect to the in-process debug server over a UNIX domain socket instead of a local TCP socket. My company has been running a variant of this PR (against a 0.6.x release) internally since last September.
start_servertakes an additionalsocket_pathargument. An error is raised if thehostparameter is also provided at the same time. I'd love suggestions on how to improve the API.The PR refactors the tests enough to allow testing both the TCP socket and UNIX domain socket variants with the same test code.