Re[4]: Can't talk to Angel debug monitor from arm-elf-gdb

[Dave Cleal <dave at cleal dot com>]

Alain,

sounds correct: and my copy of Eclipse (v3.0.1) has code to do exactly
what you say in the GDBServer case. However, I'm working with GDB
talking to the Redboot debug monitor down a serial port, so actually,
GDBServer is not involved. I've written a patch which essentially
treats this case like the GDBServer case, which I'll submit to the CDT
project in due course.

-- Dave


>> 
>> Last time I'm going to do this. Just in case anyone else ever needs
>> to know, this now all works. The trick is to patch CDT (the Eclipse
>> plugin for C/C++ development) to recognise when you're connected via a
>> serial port, and to have it start the program with a "continue"
>> command not a "run" command. Everything thereafter works.
>> 

> There was indeed a bug when using gdbserver, the state of the frontend
> was incorrect, it should have consider the inferior "suspended" so to use
> "continue" instead  "run"  since the inferior was already `loaded'.

> Maybe MI commands like,
> -target-select
> -target-attach

> should return an extra exec-async:

> *stopped

> Even if, like the case of -target-select there is no frame yet.
> It would notify to the frontends that the inferior was loaded.