remote-debugging

I'm not a Windows Phone developer, and I want as little to do as possible with anything related to Microsoft. Nonetheless, I need to get my mobile web app running properly on Windows Phone 7. What debugging tools are available for the platform? Something like the Webkit developer tools or Firebug would be ideal, either from the phone itself or more likely, remotely debugging from my computer. If such a thing doesn't exist, I'd settle for being able to read Javascript error messages, and view the contents of variables using alert() or similar. At this point, all I know is that my JS is failing:

I am trying to debug the android source using Eclipse by following the instructions found at: http://source.android.com/using-eclipse I have downloaded the source, and gotten it to build. I follow the directions in the link above and everything is fine until I run the ddms command. At this point, if Eclipse is running I get the error 'Could not open Selected VM debug port (8700)'. If I close Eclipse, then ddms runs with no problem, and I can the the processes on the emulator. However, if I now open Eclipse, I get the same error. In any case, no matter what I do, if I attempt to remote debug,

I have been struggling to debug the server side code in my app. For the client, the browser debugger in chrome or firefox work like a charm but it is more complicated for the server So here is how I managed it for meteor 0.5.6 there is no need to tinker with the run.js anymore install node-inspector https://github.com/dannycoates/node-inspector create an environment variable export NODE_OPTIONS='--debug' run meteor or mrt command. It should tell you something like debugger listening on port 5858 Once the debugger is listening, you can start node-inspector and point your browser to Visit http:/

I want to run my java code on a remote server for faster speed (The server is very powerful). What I want is to connect my Intellij to that remote server and run my code. But I want to still use the IntelliJ on my local machine (i.e. my laptop). I found a config section in IntelliJ which is in Default Setting->Build-executation-deployment-> Deployment and there I can set the address of my remote server and username and password. But I don't know what to do next. CrazyCoder There is a step by step deployment guide for PhpStorm, but for IntelliJ IDEA it would be almost the same. Here is the

I'm trying to remote debugg a chrome instance using the remote debug option in chrome: chrome.exe --remote-debugging-port=1337 as described on google page: http://code.google.com/chrome/devtools/docs/remote-debugging.html the problem is when i try to access it using IP it doesn't work, while testing it with localhost:1337 does work. any idea? You can setup an SSH tunnel in order to debug remotely. On the source machine execute: ssh -L 0.0.0.0:9223:localhost:9222 localhost -N Then on the other machine point Chrome browser to http://source-machine-ip : 9223 I don't think Chrome accepts

Is there a way to set up Remote Debugging (Msvscom.exe) on a machine that does not have Visual Studio installed? I would like to attach to the service running on the VM so I can debug an issue in the code. I've done this before but both machines have had VS installed. The Dev box is running Visual Studio 2010/Windows 7. The VM is running Windows 7 without Visual Studio. Brandon I'm going to resurrect this because anyone who's tried to do this knows it's a complete pain in the ass every time, and that it changes slightly with every possible combination of host/remote system you can have. Visual

Can anyone provide a short list of steps on how to connect a Meteor app to the WebStorm debugger please? WebStorm is the only IDE with native support for debugging Meteor server code - check this video . Even on Windows, debugging is very simple: WebStorm 9+ Go to Run --> Debug --> Edit configurations... , click the plus sign, click "Meteor". You can add environment variable like ROOT_URL if you need to. WebStorm older than 9 This answer is kept only for historical purposes. You should upgrade WebStorm. On older WebStorms, you used to have to create a Node.js debugging configuration. on the