Re: remote debugging

[Tim <Tim@deltacompsys.com>]

I understand using the open menu option, and that is what I tried.  When
'run' the app after opening the local executable, there is no connection
message on the remote device.  What appears to be happening is that
insight is running the application locally and not connecting to the
remote device.

I'm assuming that I'm doing something wrong and insight is not
attempting to connect to the remote device.

I set the target settings to:
	Target: Remote/TCP
	Hostname: 192.168.0.29
	Port: 2345
	Run Options: Attach To Target
	Run Method: Run Program

when I run a console gdb it will connect, but insigt does not...  Any
help is appreciated.  Thanx!

On Thu, 2002-12-12 at 09:29, Keith Seitz wrote:
> On 12 Dec 2002, Tim wrote:
> 
> > Do I need to "Open" the executable in Insight?  Once I do it executes
> > locally and not remotely and the remote app often terminates with an
> > error "Killing inferior".
> 
> The Run button will always do whatever it needs (or thinks it needs) to 
> start the application "running" on your target. This includes:
> 
> 1) opening an executable/debug file
> 2) gathering target communications information (debug protocol/transport)
> 3) loading executable into target memory (if needed)
> 4) "running" the target
> 
> If you don't "Open" an executable, how is the debugger to know what you 
> are debugging? It still needs debug symbols (or at least minimal symbols 
> from the executable).
> 
> Keith
> 
> 
>