Support communication with the debugged process over UNIX-domain sockets#190
Support communication with the debugged process over UNIX-domain sockets#190mbarbon wants to merge 1 commit intovim-vdebug:masterfrom
Conversation
|
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! |
|
Did this go anywhere? Anyone been running it in production? |
|
It has not been merged; I'm using the patched version |
|
Yeah, either way I'm not sure this works for xdebug php module anyway. I did not see any socket communication options for configuration. |
|
I'm using a patched version of ActiveState Komodo debuggin helper for Perl |
|
Ah I see. Do you need to use Unix sockets instead of tcp sockets? On Mon, 24 Aug 2015 19:10 Mattia Barbon notifications@github.com wrote:
|
|
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. |
|
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. |
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.