From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: [bug]org-mode with flyspell-mode freezes emacs Date: Tue, 17 Oct 2006 17:33:07 +1300 Message-ID: <17716.23811.425109.929050@kahikatea.snap.net.nz> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1161059799 7725 80.91.229.2 (17 Oct 2006 04:36:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 17 Oct 2006 04:36:39 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 17 06:36:34 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 1GZggr-0001DW-8W for ged-emacs-devel@m.gmane.org; Tue, 17 Oct 2006 06:36:33 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GZggq-0003B8-Mv for ged-emacs-devel@m.gmane.org; Tue, 17 Oct 2006 00:36:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GZggb-000394-61 for emacs-devel@gnu.org; Tue, 17 Oct 2006 00:36:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GZggY-00037f-66 for emacs-devel@gnu.org; Tue, 17 Oct 2006 00:36:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GZggX-00037Y-SR for emacs-devel@gnu.org; Tue, 17 Oct 2006 00:36:13 -0400 Original-Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GZgpj-0000Ui-Mm; Tue, 17 Oct 2006 00:45:44 -0400 Original-Received: from kahikatea.snap.net.nz (p202-124-125-135.snap.net.nz [202.124.125.135]) by viper.snap.net.nz (Postfix) with ESMTP id 941F27BA84F; Tue, 17 Oct 2006 17:36:03 +1300 (NZDT) Original-Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id 6AD2DBE452; Tue, 17 Oct 2006 17:33:08 +1300 (NZDT) Original-To: Carsten Dominik In-Reply-To: X-Mailer: VM 7.19 under Emacs 22.0.50.26 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:60809 Archived-At: > Anyway, I do now have a backtrace for this problem. Can anyone extract > something useful from this? If Emacs is hanging, a static backtrace is unlikely to be much use. You need to follow the instructions in DEBUG: If Emacs is in an infinite loop, try to determine where the loop starts and ends. The easiest way to do this is to use the GDB command `finish'. Each time you use it, Emacs resumes execution until it exits one stack frame. Keep typing `finish' until it doesn't return--that means the infinite loop is in the stack frame which you just tried to finish. Stop Emacs again, and use `finish' repeatedly again until you get back to that frame. Then use `next' to step through that frame. By stepping, you will see where the loop starts and ends. Also, examine the data being used in the loop and try to determine why the loop does not exit when it should. Also when a C backtrace is useful, it usually helps to include lisp backtrace. This is output automatically with `bt' if you run Emacs under GDB from the src directory otherwise you need to source .gdbinit (in the src directory) first. -- Nick http://www.inet.net.nz/~nickrob