This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Remote/simulator differences
- From: Daniel Jacobowitz <drow at false dot org>
- To: Jon Beniston <jon at beniston dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 19 May 2004 15:25:27 -0400
- Subject: Re: Remote/simulator differences
- References: <000c01c43dd3$f4e92390$04bda8c0@srce>
On Wed, May 19, 2004 at 08:03:22PM +0100, Jon Beniston wrote:
> Hi,
>
> I'm doing some work trying to get GDB to work with the eclipse IDE.
> However, I can't get my head around a difference between simulator and
> remote targets. With the simulator, I can do:
>
> cpu-elf-gdb prog.x
> target sim
> load
> run
>
> And the program runs fine. However, with a remote target, when I execute
> run, it says the program has already started:
>
> cpu-elf-gdb prog.x
> target remote /dev/com1
> load
> run
> The program being debugged has been started already.
> Start it from the beginning? (y or n)
>
> What's causing it to think that the program has already been started? Is
> it possible that something in the remote stub is causing this? Any
> insight would be appreciated. I'm using GDB 6.0.
For remote, the appropriate command is "continue", or sometimes "jump".
It depends on your particular target and monitor.
--
Daniel Jacobowitz