Remote/simulator differences

Remote/simulator differences

[Jon Beniston]

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.

Cheers,
JonB

Re: Remote/simulator differences

[Daniel Jacobowitz]

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

RE: Remote/simulator differences

[Jon Beniston]

> > 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.

Okay. I have hacked eclipse to take this into account. It works, but I
guess I was hoping for something a little cleaner (at least from
eclipse's perspective).

Cheers,
JonB

Re: Remote/simulator differences

[Andrew Cagney]

>>>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.
> 
> 
> Okay. I have hacked eclipse to take this into account. It works, but I
> guess I was hoping for something a little cleaner (at least from
> eclipse's perspective).

Yes.

GDB is very inconsistent when it comes to attaching / starting a target. 
  We [gdb] need to be willing to first define/fix the behavior and 
second conduct a pr exercise explaining why things are changing to our 
users.

Andrew