From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3962 invoked by alias); 18 May 2009 21:41:26 -0000 Received: (qmail 3949 invoked by uid 22791); 18 May 2009 21:41:25 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 May 2009 21:41:15 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 49A8610F4D; Mon, 18 May 2009 21:41:13 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 1B4F910F4C; Mon, 18 May 2009 21:41:13 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1M6Aa8-0007jw-5y; Mon, 18 May 2009 17:41:12 -0400 Date: Mon, 18 May 2009 21:41:00 -0000 From: Daniel Jacobowitz To: "Garrod, David" Cc: "gdb@sourceware.org" Subject: Re: How can I use the call command when analyzing a core Message-ID: <20090518214112.GA29732@caradoc.them.org> Mail-Followup-To: "Garrod, David" , "gdb@sourceware.org" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00125.txt.bz2 On Mon, May 18, 2009 at 05:29:11PM -0400, Garrod, David wrote: > 1) Is there any chance at all of working out how to change gdb to do "call" when analyzing a core on the same > architecture as the core was taken on? Basically, no. We don't have any of the internal data structures of the application in valid state. We'd have to do an emacs-style "undump" - and emacs takes all sorts of shortcuts to make this work. Something you may want to look into is the new Python binding, which makes it easier to write post-mortem inspection than the GDB CLI. -- Daniel Jacobowitz CodeSourcery