From: Daniel Jacobowitz <drow@false.org>
To: Jiju George T <jiju.george@nestgroup.net>
Cc: gdb@sourceware.org
Subject: Re: Asynchronouse progress reporting from GDB Server to gdb using Remote Serial Protocol
Date: Mon, 21 Apr 2008 18:33:00 -0000 [thread overview]
Message-ID: <20080421171858.GA14921@caradoc.them.org> (raw)
In-Reply-To: <00a201c8a3d0$25ea0d40$390aa8c0@ashmicro.ashling.com>
On Mon, Apr 21, 2008 at 05:52:56PM +0100, Jiju George T wrote:
> Hi,
>
> Â We have a GDB Server which manages connections to embedded targets. We
> have a monitor command for doing a lengthy operation on the target device.
> We want to report the status of this lengthy operation back to gdb
> periodically. Is there any support for this in GDB Remote Serial Protocol?
Not yet. But Jim Blandy drafted a proposal for progress reporting
last year, which I hope we will implement eventually. I don't think
it was posted.
For monitor commands, you could just send back an O packet with an
informative message periodically.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-04-21 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 18:26 Jiju George T
2008-04-21 18:33 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080421171858.GA14921@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jiju.george@nestgroup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox