From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27301 invoked by alias); 12 Dec 2001 23:29:36 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26683 invoked from network); 12 Dec 2001 23:28:15 -0000 Received: from unknown (HELO dr-evil.shagadelic.org) (208.176.2.162) by sources.redhat.com with SMTP; 12 Dec 2001 23:28:15 -0000 Received: by dr-evil.shagadelic.org (Postfix, from userid 7518) id 55C2B9869; Wed, 12 Dec 2001 15:28:14 -0800 (PST) Date: Wed, 12 Dec 2001 15:29:00 -0000 From: Jason R Thorpe To: Eli Zaretskii Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] New command 'gcore' Message-ID: <20011212152813.J28715@dr-evil.shagadelic.org> Reply-To: thorpej@wasabisystems.com Mail-Followup-To: Jason R Thorpe , Eli Zaretskii , msnyder@cygnus.com, gdb-patches@sources.redhat.com References: <3C17D3A0.DE140BFB@cygnus.com> <5567-Thu13Dec2001010400+0200-eliz@is.elta.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5567-Thu13Dec2001010400+0200-eliz@is.elta.co.il>; from eliz@is.elta.co.il on Thu, Dec 13, 2001 at 01:04:00AM +0200 Organization: Wasabi Systems, Inc. X-SW-Source: 2001-12/txt/msg00330.txt.bz2 On Thu, Dec 13, 2001 at 01:04:00AM +0200, Eli Zaretskii wrote: > > From: Michael Snyder > > Newsgroups: cygnus.patches.gdb > > Date: Wed, 12 Dec 2001 14:01:04 -0800 > > > > The idea is that 'gcore' would cause gdb to generate a core image > > of the inferior program (just like the 'gcore' unix command). > > The user could drop a core file at any point in the inferior's > > execution, and save the memory and register state for debugging later. > > We ought to be able to cook up an elf core file pretty easily using > > bfd. > > Sounds great! Yah, gcore is cool, but it generally requires support from the kernel in one way or another: * You need to know which chunks of the address space are actually mapped, and the protection of those regions. * You need to know if a given chunk of the address space should be dumped, even if it is mapped (consider a memory-mapped device where reads produce side-effects). * You need to know how many LWPs there are, and need to be able to iterate over them. -- -- Jason R. Thorpe