RE: protocol question

["Decker, Paul" <Paul.Decker@analog.com>]

Outstanding, my message showed up as soon as I changed the state to
running!  

Now, this means I have to change plans a little.  Is there a way to send
unsolicited messages to the gdb console (to be displayed) regardless of
the actually execution state?

Thanks,
Paul.




-----Original Message-----
From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com]
On Behalf Of Daniel Jacobowitz
Sent: Tuesday, March 22, 2005 10:33 AM
To: Decker, Paul
Cc: gdb@sources.redhat.com
Subject: Re: protocol question

On Tue, Mar 22, 2005 at 10:24:45AM -0500, Decker, Paul wrote:
>  
> Hello everyone!
> 
> 
> I apologize if this is the wrong news group for this question, if so; 
> just point me to the correct one.
> 
> I'm developing a target stub for a custom processor which will then be

> able to connect with GDB.  From what I understand, the stub can send 
> unsolicited messages to GDB, for example, if the stub encounters an 
> error of some sort, or wants to send other information to be displayed

> in the GDB console.  It seems this is done with the 'O' command being 
> sent by the stub, without the stub checking for an ack.

As you may have noticed, the 'O' packet is considerably different than
the rest of the protocol.  It doesn't fit in well with the normal
command/response model.

> Is there anything in GDB that needs to be 'turned on' to enable this 
> functionality, or do I have a conceptual problem and this is not how
it
> is designed to work?   I've tried to send a test command of:

O is actually a 'wait response'.  It's supposed to be output from the
inferior, not the stub, so GDB only expects it when the target is
running.  Try that instead.


--
Daniel Jacobowitz
CodeSourcery, LLC