remote-debugging

My scenario is this: I telework from home and log into my work machine via Windows Remote Desktop. I use Eclipse as my development environment for Android apps on my work computer. Using ADB, I would like to be able to deploy apps from my work computer to a device on my home network, for scenarios where the emulator doesn't do the app justice. I found this post, which discuss a very similar scenario, with the exception of deploying to an emulator running on a local PC, instead of deploying to a local device: http://www.41post.com/5003/programming/android-adb-remote-emulator-access I'm trying

I'm running hadoop in a single-machine, local-only setup, and I'm looking for a nice, painless way to debug mappers and reducers in eclipse. Eclipse has no problem running mapreduce tasks. However, when I go to debug, it gives me this error : 12/03/28 14:03:23 WARN mapred.JobClient: No job jar file set. User classes may not be found. See JobConf(Class) or JobConf#setJar(String). Okay, so I do some research. Apparently, I should use eclipse's remote debugging facility, and add this to my hadoop-env.sh : -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5000 I do that and I can step

We're using the Eclipse CDT 5 C++ IDE on Windows to develop a C++ application on a remote AIX host. Eclipse CDT has the ability to perform remote debugging using gdbserver. Unfortunately, gdbserver is not supported on AIX. Is anyone familiar with a way to debug remotely using Eclipse CDT without gdbserver? Perhaps using an SSH shell connection to gdb? finally I got gdb run remotly anyhow now. At the Bug-symbol on the taskbar I took Debug Configurations - GDB Hardware Debugging. In Main C/C++ Applications I set the full path on the Samba share of the executable ( X:\abin\vlmi9506 ). I also set

This question already has an answer here: How can I connect to Android with ADB over TCP? 32 answers I want to debug Android APPs on my phone (LG nexus 4). I'm travelling and I forgot my USB cable. When I work at home I can do it just connecting the USB cable and executing the command 'adb tcpip 5555'. Then I can unplug the USB cable and connect via 'adb connect IP'. But now I cannot execute the first command because I don't have a cable. I don't understand why I have to do it every time, since I already execute the 'adb tcpip' command before. What I tried now: I installed a terminal

Past scenario - Work with Tomcat and start in debug mode and Remote Debug with Eclipse. - Define a port and connect with eclipse in this debug/remote port. - Use to debug servers in other hosts/servers Today scenario Now, I'm using Jetty and I've try to do the same, but with no success, could anyone help-me with that? I did not use Maven, and did not want to start Jetty inside from my Eclipse. Environment: Windows XP Java V. 5 Jetty V. 6.1.15 Links: http:// docs.codehaus.org/display/JETTY/Debugging This did not help me! http:// docs.codehaus.org/display/JETTY/Debugging+Jetty+with+Eclipse http:

Today I ran into a problem were I needed to remote-debug a program. The program was launched from another system, so I really don't have an opportunity to interact with it on the command line. I could change its source easily though. What I needed to happen was for the program to start normally, and then wait for me to attach to it with a debugger. I couldn't come up with a way to do it that made me happy. I did find the bug, but without the help of the debugger. while(true) { } Kept the process alive, and then I could "set next statement" with the debugger, but it seemed awkward and rude.