From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15961 invoked by alias); 13 Nov 2007 22:40:09 -0000 Received: (qmail 15949 invoked by uid 22791); 13 Nov 2007 22:40:08 -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; Tue, 13 Nov 2007 22:40:07 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Is4QN-0002Cm-1F for gdb@sources.redhat.com; Tue, 13 Nov 2007 22:40:03 +0000 Received: from i577bf06d.versanet.de ([87.123.240.109]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Nov 2007 22:40:03 +0000 Received: from Stephen.Berman by i577bf06d.versanet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Nov 2007 22:40:03 +0000 To: gdb@sources.redhat.com From: Stephen Berman Subject: Re: GDB cannot access memory after Emacs abort Date: Tue, 13 Nov 2007 22:40:00 -0000 Message-ID: <87fxz9dbks.fsf@escher.local.home> References: <87r6j6rvn3.fsf@escher.local.home> <87hcjtllau.fsf@escher.local.home> <1194763094.16917.278.camel@localhost.localdomain> <87ir48gzet.fsf@escher.local.home> <1194844555.16917.319.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/msg00112.txt.bz2 On Sun, 11 Nov 2007 21:15:55 -0800 Michael Snyder wrote: > On Mon, 2007-11-12 at 00:01 +0100, Stephen Berman wrote: >> On Sun, 11 Nov 2007 09:44:23 +0200 Eli Zaretskii wrote: >> >> > the upshot of all this is that `bt' doesn't >> > work, as shown below: >> > >> >> > > (gdb) bt >> >> > > #0 abort () at emacs.c:431 >> >> > > Cannot access memory at address 0xbfd6836c >> >> > > Cannot access memory at address 0x8321b6c >> > [...] > I wonder -- after the above happens, what do you get if you > type the following at the (gdb) prompt: > > x /i $eip After the abort occurs, the desktop locks up, I switch to a virtual tty and kill -9 the emacs process, releasing the desktop, then type what you said at the gdb prompt and get this: 0x80f9e56 : Cannot access memory at address 0x80f9e56 In this case, bt returned this: Cannot access memory at address 0xbf855e4c Cannot access memory at address 0x8322c0c > If you get the same error (Cannot access memory at ...), > then perhaps gdb has lost contact with the child process > entirely, and cannot access *any* memory. Yes, this is also what Jim Blandy surmised. But, as I ask in my response to Blandy, why does the desktop lock up only happen when the emacs abort is induced while running under gdb? Steve Berman