From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15102 invoked by alias); 22 Dec 2008 22:52:54 -0000 Received: (qmail 15092 invoked by uid 22791); 22 Dec 2008 22:52:54 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 22 Dec 2008 22:52:19 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id mBMMpoU7016911; Mon, 22 Dec 2008 23:51:50 +0100 (CET) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id mBMMpmml011982; Mon, 22 Dec 2008 23:51:48 +0100 (CET) Date: Mon, 22 Dec 2008 22:52:00 -0000 Message-Id: <200812222251.mBMMpmml011982@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: eliz@gnu.org CC: drow@false.org, sergiodj@linux.vnet.ibm.com, tromey@redhat.com, msnyder@vmware.com, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org In-reply-to: (message from Eli Zaretskii on Tue, 23 Dec 2008 00:19:06 +0200) Subject: Re: RFC: "info proc map" for corefiles 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> 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/msg00398.txt.bz2 > Date: Tue, 23 Dec 2008 00:19:06 +0200 > From: Eli Zaretskii > > > 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. Agreed