From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26316 invoked by alias); 18 Dec 2008 21:44:08 -0000 Received: (qmail 26307 invoked by uid 22791); 18 Dec 2008 21:44:08 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Dec 2008 21:43:32 +0000 Received: from mailhost5.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 3DAC12E006; Thu, 18 Dec 2008 13:43:31 -0800 (PST) Received: from [10.20.92.151] (promb-2s-dhcp151.eng.vmware.com [10.20.92.151]) by mailhost5.vmware.com (Postfix) with ESMTP id 330B4DC05C; Thu, 18 Dec 2008 13:43:31 -0800 (PST) Message-ID: <494AC2D3.9090705@vmware.com> Date: Thu, 18 Dec 2008 21:44:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20080411) MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=E9rgio_Durigan_J=FAnior?= CC: Mark Kettenis , "gdb-patches@sourceware.org" Subject: Re: RFC: "info proc map" for corefiles References: <1229620702.6602.12.camel@miki> <200812181846.mBIIkTgK015985@brahms.sibelius.xs4all.nl> <1229626216.6602.15.camel@miki> In-Reply-To: <1229626216.6602.15.camel@miki> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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/msg00333.txt.bz2 Sérgio Durigan Júnior wrote: > Hello Mark, > > On Thu, 2008-12-18 at 19:46 +0100, Mark Kettenis wrote: > >> This looks pretty cool, but I think having this as "info proc" >> subcommand is wrong: >> >> (gdb) help info >> ... >> info proc -- Show /proc process information about any running process >> ... >> >> Corefiles have nothing to do with /proc and many operating systems >> don't even have such a thing. > > All right, good point. Do you have any suggestion for this? Should I > create another class of command? "info core"? There are probably a bunch of things we could expose about a core file that would not make sense for a process, and vice versa.