Skip to content

Support communication with the debugged process over UNIX-domain sockets - #190

Open
mbarbon wants to merge 1 commit into
vim-vdebug:masterfrom
mbarbon:unix-domain
Open

Support communication with the debugged process over UNIX-domain sockets#190
mbarbon wants to merge 1 commit into
vim-vdebug:masterfrom
mbarbon:unix-domain

Conversation

@mbarbon

Copy link
Copy Markdown
Contributor

I'd like to add the option for the debugger to listen on an Unix-domain socket, to avoid having a TCP port open by the debugger on a shared server (I can restrict access to the Unix-domain socket via Unix permissions).

The patch also updates the documentation.

@joonty

Copy link
Copy Markdown
Collaborator

This is great, and something that's been on my mind to do for a while.

I'll give it a test and get back to you soon. Thanks a lot!

@lkraav

Copy link
Copy Markdown

Did this go anywhere? Anyone been running it in production?

@mbarbon

Copy link
Copy Markdown
ContributorAuthor

It has not been merged; I'm using the patched version

@lkraav

Copy link
Copy Markdown

Yeah, either way I'm not sure this works for xdebug php module anyway. I did not see any socket communication options for configuration.

@joonty

Copy link
Copy Markdown
Collaborator

Hi,

I've done some playing around with this and I'm pretty sure @lkraav is right about Xdebug not supporting unix sockets. @mbarbon what language are you debugging with?

@mbarbon

Copy link
Copy Markdown
ContributorAuthor

I'm using a patched version of ActiveState Komodo debuggin helper for Perl

@joonty

Copy link
Copy Markdown
Collaborator

Ah I see. Do you need to use Unix sockets instead of tcp sockets?
Basically, what's your inspiration behind this PR? Thanks

On Mon, 24 Aug 2015 19:10 Mattia Barbon notifications@github.com wrote:

I'm using a patched version of ActiveState Komodo debuggin helper for Perl


Reply to this email directly or view it on GitHub
#190 (comment).

@mbarbon

Copy link
Copy Markdown
ContributorAuthor

I want the option of not having an "execute arbitrary code as a different user" port open while I am debugging (because of a partially shared development environment).

I realize it's not the common case, it just seemed a nice option to have.

@joonty

Copy link
Copy Markdown
Collaborator

I'm going to keep this one on ice for now - I'll look at implementing it in version 2, as I don't want to add any more features to version 1. Thanks again.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@mbarbon@joonty@lkraav