From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: C-g crash redux Date: Thu, 03 Aug 2006 01:21:16 +0200 Message-ID: References: <877j1qvp4k.fsf@pacem.orebokech.com> <17617.8764.824445.882539@kahikatea.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1154561067 21892 80.91.229.2 (2 Aug 2006 23:24:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 2 Aug 2006 23:24:27 +0000 (UTC) Cc: Romain Francoise , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 03 01:24:25 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G8Q3T-0005SR-93 for ged-emacs-devel@m.gmane.org; Thu, 03 Aug 2006 01:23:12 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G8Q3S-0001lb-JX for ged-emacs-devel@m.gmane.org; Wed, 02 Aug 2006 19:23:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G8Q3H-0001lL-8U for emacs-devel@gnu.org; Wed, 02 Aug 2006 19:22:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G8Q3G-0001l9-A5 for emacs-devel@gnu.org; Wed, 02 Aug 2006 19:22:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G8Q3G-0001l6-7R for emacs-devel@gnu.org; Wed, 02 Aug 2006 19:22:58 -0400 Original-Received: from [195.41.46.235] (helo=pfepa.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G8Q6T-0005nL-CG for emacs-devel@gnu.org; Wed, 02 Aug 2006 19:26:17 -0400 Original-Received: from kfs-l.imdomain.dk.cua.dk (0x503e2644.bynxx3.adsl-dhcp.tele.dk [80.62.38.68]) by pfepa.post.tele.dk (Postfix) with SMTP id 07A79FAC026; Thu, 3 Aug 2006 01:22:46 +0200 (CEST) Original-To: Nick Roberts In-Reply-To: <17617.8764.824445.882539@kahikatea.snap.net.nz> (Nick Roberts's message of "Thu, 3 Aug 2006 10:07:56 +1200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:58024 Archived-At: Nick Roberts writes: > Romain Francoise writes: > > I can crash Emacs reliably with current (Aug 2nd) sources by hitting C-g > > while it's preparing a partial-completion-mode prompt. I just did it > > three times in a row. The Lisp backtrace shows that it's indeed related > > to sit-for: > > Emacs can be made to crash simply by evaluating (sit-for 4) in the scratch > buffer and typing C-g before four seconds elapse. > > It's due to this change: > > 2006-08-01 Kim F. Storm > > * process.c (wait_reading_process_output_unwind): New function. > Restores waiting_for_user_input_p to saved value. > (wait_reading_process_output): Unwind protect waiting_for_user_input_p > instead of save/restore old value on stack. > > Presumably wait_reading_process_output is interrupted before it can do: > > unbind_to (count, Qnil); Huh? Is that really possible? What kind of interrupt can cause unwind_protect forms NOT to be run? I don't have time to look at this right now. Could someone pls. investigate this. (It is trivial to reproduce as Nick describes above). -- Kim F. Storm http://www.cua.dk