[Bug 1001614] eCos GDB stub "detach" reply incompatible with GDB7.4.1

[bugzilla-daemon at bugs dot ecos dot sourceware dot org]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001614

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |MODIFIED

--- Comment #3 from John Dallaway <john@dallaway.org.uk> 2012-06-25 14:40:43 BST ---
(In reply to comment #2)

> The patch isn't right. GDB is correct - the remote side doesn't know how to
> detach, hence the "null" packet rather than OK.
> 
> In all versions of GDB to date, GDB will stop talking to the target (closing
> tcp socket if needed) anyway. I assume that is still the case in 7.4.1?

It is not still the case. GDB 7.4.1 is apparently left in the same state as if
the detach command had not been issued:

(gdb) tar rem /dev/ttyS0
Remote debugging using /dev/ttyS0
0x01003688 in ?? ()
(gdb) det
Remote doesn't know how to detach
(gdb) tar rem /dev/ttyS0
A program is being debugged already.  Kill it? (y or n) y

Remote debugging using /dev/ttyS0
0x01003688 in ?? ()
(gdb) det
Remote doesn't know how to detach
(gdb) q
A debugging session is active.

        Inferior 1 [Remote target] will be killed.

Quit anyway? (y or n) y

> Presumably you don't
> actually need the correct behaviour since this patch would continue to make it
> identical to 'kill', as all this patch does is silence the message.

The rationale for the patch is just to allow us to work with eCos stubs and GDB
4.7.1 without the confusing messages and prompts shown above. Can you suggest a
better approach?

I note that some JTAG debuggers allow the interpretation of the GDB detach
command to be configured (resume execution, reset, halt, nothing) but they
always reply "OK".

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.