From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA GDB/MI] Help determine if GDB/MI command exists or not
Date: Mon, 18 Nov 2013 17:12:00 -0000 [thread overview]
Message-ID: <1384794719-20594-1-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <528631F2.40408@redhat.com>
Hello,
Re: http://www.sourceware.org/ml/gdb-patches/2013-11/msg00382.html
This series introduces 2 patches meant to help front-ends determine
whether a given GDB/MI command exists or not.
- Patch #1 introduces a new command "-info-gdb-mi-command"
The patch is very close to what was proposed in the original
RFC, with only minor corrections, based on feedback received then;
It's basically document changes, IIRC.
- Path #2 implements Pedro's idea of adding an error code to
the "^error" result record.
I took Pedro's patch nearly verbatim, removing the bits that
dealt with invalid command-line usage (this part is left for
another time, if the need becomes a little more explicit).
I did notice that the additonal variable looked an awful lot
like an error code, so I found it odd that we'd name if "error="
in the patch. And then I realized that Pedro's first email did
say "code", so I assumed it was a brain fart, and fixed the patch
to use "code".
Additional remarks on that patch inside the patch's revision log
(to be part of the commit when eventually pushed).
I added NEWS, doco, and testcase as well.
Thank you,
--
Joel
next prev parent reply other threads:[~2013-11-18 17:12 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 17:16 [RFC] Add ada-exception-catchpoints to -list-features command output Joel Brobecker
2013-11-10 22:16 ` Eli Zaretskii
2013-11-12 11:25 ` Joel Brobecker
2013-11-12 16:39 ` Eli Zaretskii
2013-11-13 3:02 ` Joel Brobecker
2013-11-11 15:22 ` Tom Tromey
2013-11-12 9:18 ` Joel Brobecker
2013-11-12 12:11 ` [RFC] New GDB/MI command "-info-gdb-mi-command" Joel Brobecker
2013-11-12 17:04 ` Eli Zaretskii
2013-11-12 17:48 ` Joel Brobecker
2013-11-12 18:34 ` Eli Zaretskii
2013-11-13 3:19 ` Joel Brobecker
2013-11-12 21:17 ` André Pönitz
2013-11-13 2:47 ` Joel Brobecker
2013-11-14 0:36 ` André Pönitz
2013-11-14 9:48 ` Joel Brobecker
2013-11-14 18:31 ` André Pönitz
2013-11-14 19:03 ` Pedro Alves
2013-11-14 19:37 ` Pedro Alves
2013-11-14 20:30 ` Tom Tromey
2013-11-15 5:35 ` Joel Brobecker
2013-11-15 12:39 ` Pedro Alves
2013-11-15 14:38 ` Joel Brobecker
2013-11-15 14:40 ` Pedro Alves
2013-11-18 17:12 ` Joel Brobecker [this message]
2013-11-18 17:13 ` [RFA 1/2] " Joel Brobecker
2013-11-18 17:29 ` Eli Zaretskii
2013-11-19 4:35 ` Joel Brobecker
2013-11-19 16:11 ` Eli Zaretskii
2013-12-02 3:26 ` Joel Brobecker
2013-12-02 3:51 ` Eli Zaretskii
2013-12-02 4:41 ` Joel Brobecker
2013-12-02 14:53 ` Pedro Alves
2013-12-03 4:06 ` pushed: " Joel Brobecker
2013-11-18 17:21 ` [RFA 2/2] Add "undefined-command" error code at end of ^error result Joel Brobecker
2013-11-18 17:29 ` Eli Zaretskii
2013-11-19 6:02 ` Joel Brobecker
2013-11-19 16:16 ` Eli Zaretskii
2013-11-19 11:19 ` Pedro Alves
2013-11-20 3:46 ` Joel Brobecker
2013-12-03 4:08 ` pushed: " Joel Brobecker
2013-11-19 15:05 ` [RFA GDB/MI] Help determine if GDB/MI command exists or not Pedro Alves
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=1384794719-20594-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@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