From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15139 invoked by alias); 11 Nov 2007 19:22:48 -0000 Received: (qmail 15130 invoked by uid 22791); 11 Nov 2007 19:22:48 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 11 Nov 2007 19:22:41 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id E3A329835C; Sun, 11 Nov 2007 19:22:38 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id AD8269835B; Sun, 11 Nov 2007 19:22:38 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1IrIOD-00034E-BM; Sun, 11 Nov 2007 14:22:37 -0500 Date: Sun, 11 Nov 2007 19:22:00 -0000 From: Daniel Jacobowitz To: Michael Snyder Cc: Stephen Berman , gdb@sources.redhat.com Subject: Re: GDB cannot access memory after Emacs abort Message-ID: <20071111192237.GA11728@caradoc.them.org> Mail-Followup-To: Michael Snyder , Stephen Berman , gdb@sources.redhat.com References: <87r6j6rvn3.fsf@escher.local.home> <87hcjtllau.fsf@escher.local.home> <1194763094.16917.278.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1194763094.16917.278.camel@localhost.localdomain> User-Agent: Mutt/1.5.15 (2007-04-09) 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/msg00085.txt.bz2 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 just from observation, I don't know much about X programming. -- Daniel Jacobowitz CodeSourcery