From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2552 invoked by alias); 11 Nov 2007 23:10:08 -0000 Received: (qmail 2540 invoked by uid 22791); 11 Nov 2007 23:10: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; Sun, 11 Nov 2007 23:10:06 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1IrLwI-0007me-Pv for gdb@sources.redhat.com; Sun, 11 Nov 2007 23:10:02 +0000 Received: from i577bf47d.versanet.de ([87.123.244.125]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 11 Nov 2007 23:10:02 +0000 Received: from Stephen.Berman by i577bf47d.versanet.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 11 Nov 2007 23:10:02 +0000 To: gdb@sources.redhat.com From: Stephen Berman Subject: Re: GDB cannot access memory after Emacs abort Date: Sun, 11 Nov 2007 23:10:00 -0000 Message-ID: <87hcjsgzea.fsf@escher.local.home> References: <87r6j6rvn3.fsf@escher.local.home> <87hcjtllau.fsf@escher.local.home> <1194763094.16917.278.camel@localhost.localdomain> <20071111192237.GA11728@caradoc.them.org> 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/msg00088.txt.bz2 On Sun, 11 Nov 2007 14:22:37 -0500 Daniel Jacobowitz wrote: > On Sat, Nov 10, 2007 at 10:38:14PM -0800, Michael Snyder wrote: >> > > At this point my desktop (I tried in KDE, GNOME and twm, same behavior >> > > in all) is totally locked up, but I can switch to a virtual tty and >> > > there kill emacs with SIGKILL (kill -9); SIGTERM (kill -15) does not do >> > > the job. >> >> Making sure that I understand -- you ran emacs under gdb, >> you set a breakpoint at abort, you hit the breakpoint -- >> and your desktop is locked up? >> >> That seems unusual -- do you have any idea of the cause? > > This is pretty common when debugging X programs, IIRC. I believe > there's some ways in which an application can "own" a display while > something is in progress. That's interesting; do you have any pointers to further information about this? Yet, as I mentioned in my other followups, this has never happened to me before when running Emacs under gdb, even when it's in an infinite loop. It sounds like you, too, don't suspect a bug in GDB that prevented getting a backtrace. Steve Berman