From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5789 invoked by alias); 5 May 2009 16:53:22 -0000 Received: (qmail 5781 invoked by uid 22791); 5 May 2009 16:53:21 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 May 2009 16:53:14 +0000 Received: (qmail 16879 invoked from network); 5 May 2009 16:53:08 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 May 2009 16:53:08 -0000 From: Pedro Alves To: gdb-patches@sourceware.org, danny.backx@scarlet.be Subject: Re: Post mortem debugging for Windows CE Date: Tue, 05 May 2009 16:53:00 -0000 User-Agent: KMail/1.9.10 References: <1240929901.29047.110.camel@dannypc> <200905011637.17476.pedro@codesourcery.com> <1241530252.500.95.camel@dannypc> In-Reply-To: <1241530252.500.95.camel@dannypc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905051753.45227.pedro@codesourcery.com> 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: 2009-05/txt/msg00087.txt.bz2 On Tuesday 05 May 2009 14:30:51, Danny Backx wrote: > It looks like I'm getting close to something that works. Small session > below. Cleanup and more testing are certainly required. This is looking very good! > I'm about to look into your suggestion about .module sections. > > How can I observe the effect of that ? How can I test ? The .modules sections would contain the list of loaded modules at the time of the crash. So, 'info sharedlibrary' should list the same list of dlls as the live inferior had, and their load addresses should be the same. You could tweak your test app to move the crashing code into a mini dll you'd write. Use 'set sysroot' or 'set solib-search-path' command to point GDB at the host copy of the dll, and load the minidump into GDB. GDB should be able to show you the crash site source code, backtracing from the function in the dll should work, and 'info sharedlibrary' should report correct data, of course. -- Pedro Alves