From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: bpisupat@cs.indiana.edu, gdb@sources.redhat.com
Subject: Re: MI starting guide
Date: Sat, 12 Mar 2005 10:30:00 -0000 [thread overview]
Message-ID: <01c526ee$Blat.v2.4$37bafb40@zahav.net.il> (raw)
In-Reply-To: <20050312000437.GA17327@white> (message from Bob Rossi on Fri, 11 Mar 2005 19:04:37 -0500)
> Date: Fri, 11 Mar 2005 19:04:37 -0500
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb@sources.redhat.com
>
> There is no user document that I know of that describes how to write an
> FE on top of GDB using the MI interface besides the manual.
Sad, but true.
Actually, the MI documentation in the manual was once a separate
manual which was not compiled into gdb.info. I did some minimal work
to integrate it into gdb.texinfo (because I believe that some
documentation is better than no documentation), but I won't pretend
that the result is in good shape, and I don't know enough about MI to
improve those parts of the manual in useful ways.
> AFAIK, FE's use fork/exec with GDB and communicate with it over a pipe
> like you suggested. Beware, some of the MI commands that the manual says
> are there are unimplemented.
>
> If you want to see some interaction between GDB and another process look
> at the gdb.mi testsuite.
I'm urging people who work with the MI interface, such as Nick and
Bob, to please contribute additions to the manual (either gdb.texinfo
or gdbint.texinfo) that describe what you found out during your work
that you wish has been there to begin with. There is no better source
of useful information than those who actually need it to do some job.
If you are unsure how or where best to describe what you think is
important, don't hesitate to post your thoughts here and start a
discussion.
TIA
next prev parent reply other threads:[~2005-03-12 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 23:48 Bhanu Nagendra Pisupati
2005-03-12 0:05 ` Bob Rossi
2005-03-12 10:30 ` Eli Zaretskii [this message]
2005-03-12 14:40 ` Bob Rossi
2005-03-12 17:13 ` Eli Zaretskii
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='01c526ee$Blat.v2.4$37bafb40@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--cc=bpisupat@cs.indiana.edu \
--cc=gdb@sources.redhat.com \
/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