From: Pedro Alves <palves@redhat.com>
To: Johannes Bauer <dfnsonfsduifb@gmx.de>
Cc: gdb@sourceware.org
Subject: Re: Building gdb frontend
Date: Fri, 07 Sep 2012 10:46:00 -0000 [thread overview]
Message-ID: <5049D063.5000509@redhat.com> (raw)
In-Reply-To: <5049CE37.4020005@gmx.de>
On 09/07/2012 11:36 AM, Johannes Bauer wrote:
> Is there a preferred way to talk to gdb in a
> "machine-readable" friendly way so I know exactly when gdb is ready to
> receive commands again?
See "The gdb/mi Interface" in the manual.
--
Pedro Alves
next prev parent reply other threads:[~2012-09-07 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 10:36 Johannes Bauer
2012-09-07 10:46 ` Pedro Alves [this message]
2012-09-07 11:05 ` Johannes Bauer
2012-09-07 16:42 ` Andrew Burgess
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=5049D063.5000509@redhat.com \
--to=palves@redhat.com \
--cc=dfnsonfsduifb@gmx.de \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).