remote-debugging

问题 So I have set up a docker on my laptop. I'm using Boot2Docker so I have one level of indirection to access the docker. In PyCharm, I can set a remote python interpreter via SSH but I'm not sure how to do it for dockers that can only be accessed via Boot2Docker? 回答1: Okay so to answer your question(s): In PyCharm, I can set a remote python interpreter via SSH but I'm not sure how to do it for dockers that can only be accessed via Boot2Docker? You need: To ensure that you have SSH running in

问题 I am fairly new to remote debugging in Visual Studio, and by new I mean I have never done it before. Here are the steps I have taken to try to remotely debug an application on one of the servers in our network: open a website in VS2008 "\\server\website" Start the msvsmon service on "server" with "no authentication" and "allow any user to debug" From VS2008, Attach to the w3wp process on "server" using remote transport debugging starts and everything seems ok, but when i go to the page with

问题 Because my RCP eclipse application fails when run outside of eclipse, but works correctly when running inside of eclipse, I am attempting to use eclipse to remotely debug my application as it's running outside of the eclipse environment. I am using 32 bit Eclipse 3.6.1 on a 64 bit Windows 7 machine. I am using 32 bit Java 1.6 update 37. I use the Eclipse Product export wizard to package the app, and I end up with an eclipse.exe. I have created a Remote Debug Configuration and set it to use

问题 I'm trying to setup a dockered AMP environment and can't get the remote debugger working. My setup is as follows: I have a database container running mysql which is working like a charm. I built a Docker image 'phpmysqli' with the following Dockerfile FROM php:apache RUN docker-php-ext-install mysqli mbstring # zend_extension=/usr/local/lib/php/extensions/no-debug-non-zts-20131226/xdebug.so RUN pecl install xdebug RUN echo 'zend_extension = /usr/local/lib/php/extensions/no-debug-non-zts

问题 I test through Jasmine, Karma and a variety of browsers. I'm currently debugging a test that fails only in PhantomJS. I'd like to debug this call, so I've setup a custom PhantomJS launcher in karma that runs it with the debug port open. I'm able to access the remote debugger in Chrome through that port, however, it seems to know nothing about any of my test files. It reports an "about:blank" and a "localhost:9876" (the karma server that Phantom is hitting) but when I try to debug that

问题 Sometimes I am doing simple fixes for rather huge Java application and I don't want to open Eclipse for this task. Eclipse starts long and since the project is build out of large number of subprojects, which are build anyway by Maven, it takes ages before Eclipse is usable (at least ages in impatient Java developer scale). Almost everything I need can be done in Sublime Text editor, however one place where Eclipse shines is debugger. My workflow is: make a fix, then test it running

问题 I'm trying to debug remotely an application that's being hosted on Linux "Debian GNU/Linux 8 (jessie)" with .NET Command Line Tools (2.1.500) I'm connecting via Visual Studio via SSH and I've tried both modes: Managed .NET Core for Unix Native (GDB) Project has been compiled on Windows dotnet publish --configuration Release -r linux-x64 and also dotnet publish --configuration Debug -r linux-x64 and works perfectly fine, but for some reason I'm receiving: Managed .NET Core for Unix : Fail to

问题 I've just started to work on a MVC project. It's a web portal. I've set my sites on my local IIS 6.0 But when I want to start debugging, I get this error: Unable to start debugging on the web server. The debugger cannot connect to the remote computer. The debugger was unable to resolve the specified computer name. I don't understand that when I want to debug my project locally, what "Remote computer" it's talking about??!! Please help me guys, this is my first task in this company and I have

问题 I am trying to remote debug an Asp.Net Core Web Application (with Web API) project deployed as an Azure App Service with Visual Studio 2017 Professional. Followed the instructions as documented here. Essentially, using the Server Explorer-->App Service-->Attach Debugger Also, enabled the necessary firewall ports as mentioned. The ones I opened are TCP (4022, 4023) and UDP (3702). Also, ensure remote debugger application is in allowed list of apps in Windows Firewall. Documentation for the

问题 I'm asking my network admin to open up ports on the firewall to allow remote debugging. It says in the documentation on MSDN that it needs UDP 135. However, the admin says that a number of non-standard 19xx ports are being used. Exactly what ports are required for remote debugging to work? 回答1: You need to open ports on both your computer and the remote computer. Primarily it's TCP 135 not UDP 135. All the ports and steps are listed here: http://msdn.microsoft.com/en-us/library/h0d7tte4(v=vs