From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [bug]org-mode with flyspell-mode freezes emacs Date: Tue, 17 Oct 2006 14:40:33 -0400 Message-ID: References: <17716.23811.425109.929050@kahikatea.snap.net.nz> <4d08b83ef805bfb7828085d8e1f67daf@science.uva.nl> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1161110485 15666 80.91.229.2 (17 Oct 2006 18:41:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 17 Oct 2006 18:41:25 +0000 (UTC) Cc: nickrob@snap.net.nz, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 17 20:41:23 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 1GZts7-0006wB-Fp for ged-emacs-devel@m.gmane.org; Tue, 17 Oct 2006 20:41:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GZts6-0001Cy-Sk for ged-emacs-devel@m.gmane.org; Tue, 17 Oct 2006 14:41:02 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GZtri-00019y-MZ for emacs-devel@gnu.org; Tue, 17 Oct 2006 14:40:38 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GZtri-00019W-0M for emacs-devel@gnu.org; Tue, 17 Oct 2006 14:40:38 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GZtrh-00019Q-Mc for emacs-devel@gnu.org; Tue, 17 Oct 2006 14:40:37 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GZtrg-0004yS-7q for emacs-devel@gnu.org; Tue, 17 Oct 2006 14:40:36 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1GZtrd-0006lT-49; Tue, 17 Oct 2006 14:40:33 -0400 Original-To: Carsten Dominik In-reply-to: <4d08b83ef805bfb7828085d8e1f67daf@science.uva.nl> (message from Carsten Dominik on Tue, 17 Oct 2006 12:57:22 +0200) 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:60825 Archived-At: I have not been able to do this well, the results are very confusing to me, I sometimes end up in the garbage collection, sometimes in search functions like looking-at-1 or search-buffer. This problem is not in GC. We know that GC is simply being called over and over. So if it is in GC when you stop it, just continue and stop it again. Only the cases outside GC are interesting. A typical lisp backtrace looks like this: Lisp Backtrace: "flyspell-get-word" (0x3800209) "flyspell-word-search-backward" (0x1add4e3) "flyspell-word" (0x3800209) "flyspell-post-command-hook" (0x0) "run-hooks" (0x3809c69) or Lisp Backtrace: "re-search-forward" (0x1b0d1b3) This proves that the loop is in a loop that calls re-search-forward, but not re-search-forward. However, the loop in flyspell-get-word does not call re-search-forward. I think that means that the loop is in a higher level frame. Can you use the Lisp debugger to arrange to stop on returning to the various frames, and then continue, and thus see which frames get returned to?