From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23868 invoked by alias); 24 Jul 2009 18:54:22 -0000 Received: (qmail 23856 invoked by uid 22791); 24 Jul 2009 18:54:21 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 24 Jul 2009 18:54:11 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KNA00200V1N8800@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Fri, 24 Jul 2009 21:54:08 +0300 (IDT) Received: from HOME-C4E4A596F7 ([77.127.234.6]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KNA00I91V674S50@i_mtaout3.012.net.il>; Fri, 24 Jul 2009 21:54:08 +0300 (IDT) Date: Fri, 24 Jul 2009 20:42:00 -0000 From: Eli Zaretskii Subject: Re: [RFA] Add interface for registering JITed code In-reply-to: <9a9942200907240946q1546646ft6e9112f263bcefdf@mail.gmail.com> To: Reid Kleckner Cc: tromey@redhat.com, gdb-patches@sourceware.org, unladen-swallow@googlegroups.com Reply-to: Eli Zaretskii Message-id: <83iqhh52un.fsf@gnu.org> References: <9a9942200907221615o570e749fh5cb186c1600f159c@mail.gmail.com> <9a9942200907240946q1546646ft6e9112f263bcefdf@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00604.txt.bz2 > From: Reid Kleckner > Date: Fri, 24 Jul 2009 09:46:52 -0700 > Cc: gdb-patches@sourceware.org, unladen-swallow@googlegroups.com > > > Given that this will be a supported way for GDB to connect to JITs, I > > think that the official interface (symbol names, types, enum values, > > etc) should be documented in the GDB manual somewhere. > > Where should this go? It doesn't really fit under any of the > top-level topics, so far as I can tell. Sorry to chime in this late (patches posted as binary attachments usually discourage me from looking at them), but I cannot answer the question at this time, given what I know about this feature. Maybe if you post what you think should be described in the manual, I can make up my mind then. > > This patch also deserves an entry in NEWS. > > Done. Unfortunately, the NEWS entry is not instrumental enough. It doesn't tell the user how to use the feature. Is it possible to come up with a more useful entry?