Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "tromey@redhat.com" <tromey@redhat.com>
Cc: "Paul Pluzhnikov" <ppluzhnikov@google.com>,
	"André Pönitz" <andre.poenitz@nokia.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Learn function name by its address
Date: Fri, 26 Jun 2009 18:50:00 -0000	[thread overview]
Message-ID: <4A451826.3010709@vmware.com> (raw)
In-Reply-To: <m38wjedg42.fsf@fleche.redhat.com>

Tom Tromey wrote:
>>>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:
> 
> Paul> I think removing them would be incorrect: they do exist, MI accepts them,
> Paul> they just don't work :-(
> 
> Ugh.  That seems even worse.
> 
> Paul> Perhaps add a "NOTE: This command has not yet been implemented"
> Paul> to each one?
> 
> Or also nuke the non-working entries from the MI command table.
> I can't think of a reason we'd want to have non-functional commands.
> I'm sure we'd reject a new patch that added such a command.

What about just commenting them out, so that the work isn't lost
and someone may some day implement them?

Same for the docs -- can they be left in the source and just commented out?



  reply	other threads:[~2009-06-26 18:50 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 [this message]
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

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=4A451826.3010709@vmware.com \
    --to=msnyder@vmware.com \
    --cc=andre.poenitz@nokia.com \
    --cc=gdb@sourceware.org \
    --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