From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.bugs Subject: bug#11350: Nasty hangup Date: Sat, 07 Jul 2012 17:09:53 +0800 Message-ID: <87wr2glyxq.fsf@gnu.org> References: <8762cmzl0x.fsf@gmail.com> <83k412ip7m.fsf@gnu.org> <87ehr9nuxq.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1341652269 18667 80.91.229.3 (7 Jul 2012 09:11:09 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 7 Jul 2012 09:11:09 +0000 (UTC) Cc: 11350@debbugs.gnu.org To: Antoine Levitt Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jul 07 11:11:06 2012 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SnR2f-0003KE-E6 for geb-bug-gnu-emacs@m.gmane.org; Sat, 07 Jul 2012 11:11:05 +0200 Original-Received: from localhost ([::1]:36483 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SnR2e-0004YC-AG for geb-bug-gnu-emacs@m.gmane.org; Sat, 07 Jul 2012 05:11:04 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:52659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SnR2b-0004Y6-Ji for bug-gnu-emacs@gnu.org; Sat, 07 Jul 2012 05:11:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SnR2Z-0004DF-U5 for bug-gnu-emacs@gnu.org; Sat, 07 Jul 2012 05:11:01 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:44257) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SnR2Z-0004DB-Qy for bug-gnu-emacs@gnu.org; Sat, 07 Jul 2012 05:10:59 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1SnR7S-0000ZQ-9F for bug-gnu-emacs@gnu.org; Sat, 07 Jul 2012 05:16:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Chong Yidong Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 07 Jul 2012 09:16:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 11350 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 11350-submit@debbugs.gnu.org id=B11350.134165250832013 (code B ref 11350); Sat, 07 Jul 2012 09:16:02 +0000 Original-Received: (at 11350) by debbugs.gnu.org; 7 Jul 2012 09:15:08 +0000 Original-Received: from localhost ([127.0.0.1]:53802 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1SnR6Y-0008Ig-Q5 for submit@debbugs.gnu.org; Sat, 07 Jul 2012 05:15:07 -0400 Original-Received: from fencepost.gnu.org ([208.118.235.10]:46364) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1SnR6V-0008EH-N8 for 11350@debbugs.gnu.org; Sat, 07 Jul 2012 05:15:04 -0400 Original-Received: from [155.69.186.151] (port=33261 helo=ulysses) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1SnR1a-0003Hr-Em; Sat, 07 Jul 2012 05:09:59 -0400 In-Reply-To: <87ehr9nuxq.fsf@gmail.com> (Antoine Levitt's message of "Fri, 27 Apr 2012 15:52:33 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:61680 Archived-At: Antoine Levitt writes: >>> I'm seeing a very nasty bug, description below. I use bzr trunk and >>> update it quite regularly, but the last commits seem pretty harmless >>> ... the only change I can see in my environment is that I started using >>> org-clock today. The bugs happened when I was working, using python with >>> a comint interaction buffer. >>> >>> So anyway, when it happens, I get 100% CPU usage, and emacs just >>> hangs. I can only get out of it by sending it a SIGUSR2. > > I haven't had this bug again, if I do I'll attach a gdb and see. Have you been able to reproduce this bug?