From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27257 invoked by alias); 19 Dec 2008 16:25:17 -0000 Received: (qmail 27245 invoked by uid 22791); 19 Dec 2008 16:25:17 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BARRACUDA_BRBL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout4.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 19 Dec 2008 16:24:37 +0000 Received: from conversion-daemon.i_mtaout4.012.net.il by i_mtaout4.012.net.il (HyperSendmail v2004.12) id <0KC400L00TNQK900@i_mtaout4.012.net.il> for gdb-patches@sourceware.org; Fri, 19 Dec 2008 18:27:01 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.127.241.241]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KC400F4GTP0ES80@i_mtaout4.012.net.il>; Fri, 19 Dec 2008 18:27:01 +0200 (IST) Date: Fri, 19 Dec 2008 16:25:00 -0000 From: Eli Zaretskii Subject: Re: RFC: "info proc map" for corefiles In-reply-to: X-012-Sender: halo1@inter.net.il To: tromey@redhat.com Cc: sergiodj@linux.vnet.ibm.com, msnyder@vmware.com, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT References: <1229620702.6602.12.camel@miki> <200812181846.mBIIkTgK015985@brahms.sibelius.xs4all.nl> <1229626216.6602.15.camel@miki> <494AC2D3.9090705@vmware.com> <1229702034.6602.18.camel@miki> 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: 2008-12/txt/msg00349.txt.bz2 > Cc: Michael Snyder , Mark Kettenis , "gdb-patches\@sourceware.org" > From: Tom Tromey > Date: Fri, 19 Dec 2008 09:05:20 -0700 > > >>>>> "Sérgio" == Sérgio Durigan Júnior writes: > > Sérgio> Ok, I'll create the "info core" command for that. Thanks for the > Sérgio> comment. > > I agree that "info proc" a misnomer. But, it seems to me it would be > nice for the user to use the same command in both cases. How about a > new command (not "info core"), with the old "info proc map" aliased to > it? We don't need an alias for that; it's enough for "info proc map" subroutines to call the subroutines of "info core" internally, when the target is a core file.