On Sat, Mar 21, 2009 at 2:29 PM, Thomas Hruska <[email protected]> wrote:
> VC++ has a remote debugger as well but I've found it...wanting. You
> have to start a process up on the remote computer and then connect to it
> via TCP/IP (IMO, the most reliable connection method of the choices
> available) from the IDE and pray you get the IP address right (and the
> remote command-line options and have no weird firewall issues) the first
> time or the whole IDE hangs for about two minutes before it figures out
> there was operator error. Plus you have to build locally and move the
> binaries over to the remote machine. Minor changes to the source code =
> major pain in the neck to get the binaries over to the remote machine
> (forgetting to do so and just starting to debug = bad idea too).
> Communicating over the Internet to debug an app remotely via TCP/IP is
> about the most painful thing you can do in VC++ with the same thing over
> a LAN or VMWare (where I mainly use the remote debugger) being the
> second most painful. And if you aren't fast enough or on a flaky
> connection, the dropped TCP/IP connection creates a whole new set of
> headaches.
I've used Eclipse in that manner... but I really meant logging into a
server remotely and debugging directly on the server.
> Maybe I just use it all wrong?
> (Or maybe I misunderstood the remote gdb context?)
>
> Sun has advanced tracing abilities. Why would you need a debugger? ;)
I've had to use dbx before -- for examining core files from crashed software.
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
