From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6979 invoked by alias); 12 Nov 2007 07:39:02 -0000 Received: (qmail 6967 invoked by uid 22791); 12 Nov 2007 07:39:01 -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; Mon, 12 Nov 2007 07:38:54 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IrTsb-0004cW-UE for gdb@sources.redhat.com; Mon, 12 Nov 2007 07:38:45 +0000 Received: from 77.246.241.246 ([77.246.241.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Nov 2007 07:38:45 +0000 Received: from ghost by 77.246.241.246 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Nov 2007 07:38:45 +0000 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: GDB cannot access memory after Emacs abort Date: Mon, 12 Nov 2007 07:39:00 -0000 Message-ID: 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 Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.10.4 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/msg00093.txt.bz2 Daniel Jacobowitz wrote: > On Sat, Nov 10, 2007 at 10:38:14PM -0800, Michael Snyder wrote: >> >> 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. I believe it's XGrabPointer, which causes all mouse and/or keyboard event to be delivered to specific application. If that application is stopped by gdb, it means, in effect, that events are not processed at all. I have no idea if that's the cause, since the emacs diff posted in another email does not have any apparent locking thing, but it very likely. >> > > At this point my desktop (I tried in KDE, GNOME and twm, same >> > > behavior in all) I believe this is dependent on what toolkit the application being debugged uses, not what other applications are running. - Volodya