From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20712 invoked by alias); 14 Nov 2007 09:55:15 -0000 Received: (qmail 20656 invoked by uid 22791); 14 Nov 2007 09:55:14 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 Nov 2007 09:55:11 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1IsExa-0004OJ-IZ for gdb@sources.redhat.com; Wed, 14 Nov 2007 09:55:02 +0000 Received: from i577bc647.versanet.de ([87.123.198.71]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Nov 2007 09:55:02 +0000 Received: from Stephen.Berman by i577bc647.versanet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Nov 2007 09:55:02 +0000 To: gdb@sources.redhat.com From: Stephen Berman Subject: Re: GDB cannot access memory after Emacs abort Date: Wed, 14 Nov 2007 09:55:00 -0000 Message-ID: <873av9i2b6.fsf@escher.local.home> References: <87r6j6rvn3.fsf@escher.local.home> <87hcjtllau.fsf@escher.local.home> <1194763094.16917.278.camel@localhost.localdomain> <87k5oogzf3.fsf@escher.local.home> <1194843988.16917.310.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) 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: 2007-11/txt/msg00129.txt.bz2 On Sun, 11 Nov 2007 21:06:28 -0800 Michael Snyder wrote: [...] > To pursue it further, we can go one of two ways: > > A) maybe you can provide us with enough information and > context to reproduce the problem ourselves? This seems > unlikely, but maybe, for instance, you know that with > a certain released version of emacs and a certain released > version of linux, you can give a fixed sequence of commands > and reliably reproduce the crash? > > or > > B) we can keep asking you for more information, question > and answer style. > > For instance, I'd like to know the output that you get > from the following gdb commands when you're at the breakpoint: > > i) info registers > ii) info target > iii) x /64x $esp I posted a followup providing the requested information but it hasn't yet appeared on the list, perhaps because it was too long (the output of `info target' was 1815 lines long). Since I've gotten a backtrace in the mean time (see my followup to your suggestion to attach the emacs process to gdb), do you want me to repost or email you this information, or is it no longer relevant? Steve Berman