From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27991 invoked by alias); 11 Apr 2012 21:48:44 -0000 Received: (qmail 27983 invoked by uid 22791); 11 Apr 2012 21:48:43 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Apr 2012 21:48:31 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 2DEB51C6A09; Wed, 11 Apr 2012 17:48:30 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id x0+rkzPwhB8r; Wed, 11 Apr 2012 17:48:30 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id EBCA01C69F1; Wed, 11 Apr 2012 17:48:29 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 93255145616; Wed, 11 Apr 2012 14:48:22 -0700 (PDT) Date: Wed, 11 Apr 2012 21:48:00 -0000 From: Joel Brobecker To: Carlos O'Donell Cc: gdb@sourceware.org Subject: Re: Useful MI functions marked @ignore in gdb/doc/gdb.texinfo. Message-ID: <20120411214822.GN25623@adacore.com> References: <4F85F7F1.1070304@mentor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F85F7F1.1070304@mentor.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-04/txt/msg00075.txt.bz2 > What's the story with these hidden, but documented MI functions? This was a long time ago. My guess is that these commands were part of the initial design, and the design got captured as a hidden part of the documentation, but the commands themselves never got implemented. Most of the time, it's mostly a matter of writing the code... They usually get implemented when someone really needing the functionality just goes ahead and implements it. -- Joel