From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: tromey@redhat.com, ppluzhnikov@google.com,
andre.poenitz@nokia.com, gdb@sourceware.org
Subject: Re: Learn function name by its address
Date: Sat, 27 Jun 2009 09:40:00 -0000 [thread overview]
Message-ID: <83hby2ypzp.fsf@gnu.org> (raw)
In-Reply-To: <4A451826.3010709@vmware.com>
> Date: Fri, 26 Jun 2009 11:49:10 -0700
> From: Michael Snyder <msnyder@vmware.com>
> CC: Paul Pluzhnikov <ppluzhnikov@google.com>, =?ISO-8859-1?Q?Andr=E9_P=F6?= =?ISO-8859-1?Q?nitz?= <andre.poenitz@nokia.com>, "gdb@sourceware.org" <gdb@sourceware.org>
>
> Same for the docs -- can they be left in the source and just commented out?
If someone wants to submit a patch that comments out unimplemented MI
commands, please use @ignore..@end ignore, and please make sure (by
looking at the code) that these commands are indeed unimplemented.
Please do NOT assume that any command which says "N.A." in Example is
necessarily unimplemented.
P.S. The reason that we have unimplemented commands in this part of
the manual is that it was produced from a white paper that described
the projected implementation of MI, when most of it was still on
paper.
prev parent reply other threads:[~2009-06-27 9:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 15:43 Dmitry Dzhus
2009-06-25 15:53 ` Paul Pluzhnikov
2009-06-25 18:27 ` Michael Snyder
2009-06-25 18:36 ` Dmitry Dzhus
2009-06-25 19:14 ` Paul Pluzhnikov
2009-06-26 11:30 ` Nick Roberts
2009-06-26 16:07 ` Dmitry Dzhus
2009-06-26 6:38 ` André Pönitz
2009-06-26 7:05 ` Paul Pluzhnikov
2009-06-26 17:26 ` Tom Tromey
2009-06-26 17:35 ` Paul Pluzhnikov
2009-06-26 18:06 ` Tom Tromey
2009-06-26 18:50 ` Michael Snyder
2009-06-26 18:54 ` Paul Pluzhnikov
2009-06-26 19:19 ` Tom Tromey
2009-06-26 22:41 ` Joel Brobecker
2009-06-27 9:40 ` Eli Zaretskii [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=83hby2ypzp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andre.poenitz@nokia.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=ppluzhnikov@google.com \
--cc=tromey@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