From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4415 invoked by alias); 22 Dec 2008 22:19:53 -0000 Received: (qmail 4406 invoked by uid 22791); 22 Dec 2008 22:19:52 -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 mtaout7.012.net.il (HELO mtaout7.012.net.il) (84.95.2.19) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 22 Dec 2008 22:19:13 +0000 Received: from conversion-daemon.i-mtaout7.012.net.il by i-mtaout7.012.net.il (HyperSendmail v2007.08) id <0KCA00900TYI9C00@i-mtaout7.012.net.il> for gdb-patches@sourceware.org; Tue, 23 Dec 2008 00:21:40 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.252.83]) by i-mtaout7.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KCA00BS8U3TMN50@i-mtaout7.012.net.il>; Tue, 23 Dec 2008 00:21:30 +0200 (IST) Date: Mon, 22 Dec 2008 22:19:00 -0000 From: Eli Zaretskii Subject: Re: RFC: "info proc map" for corefiles In-reply-to: <20081222202532.GA31896@caradoc.them.org> X-012-Sender: halo1@inter.net.il To: Daniel Jacobowitz Cc: sergiodj@linux.vnet.ibm.com, tromey@redhat.com, msnyder@vmware.com, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <1229626216.6602.15.camel@miki> <494AC2D3.9090705@vmware.com> <1229702034.6602.18.camel@miki> <1229703833.6602.28.camel@miki> <1229960072.27356.0.camel@miki> <1229975651.27356.2.camel@miki> <20081222202532.GA31896@caradoc.them.org> 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/msg00397.txt.bz2 > Date: Mon, 22 Dec 2008 15:25:32 -0500 > From: Daniel Jacobowitz > Cc: =?iso-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= , > tromey@redhat.com, msnyder@vmware.com, mark.kettenis@xs4all.nl, > gdb-patches@sourceware.org > > I wonder if we should rename or redefine "info proc". It is currently > /proc specific, so Sergio's new work for core files doesn't belong > there. But while it exists we can't reasonably add a separate "info > process". > > Or should we fold this into "info inferior" and make it work for other > kinds of inferiors? I'm okay with both of these ways, but "info process" doesn't sound like a good name for core files, IMO.