unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [bug]org-mode with flyspell-mode freezes emacs
Date: Tue, 17 Oct 2006 17:33:07 +1300	[thread overview]
Message-ID: <17716.23811.425109.929050@kahikatea.snap.net.nz> (raw)
In-Reply-To: <d7ff1188473a01ddecff5369943062b1@science.uva.nl>

 > 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

  parent reply	other threads:[~2006-10-17  4:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15  4:20 [bug]org-mode with flyspell-mode freezes emacs Richard Stallman
2006-10-16  7:55 ` Carsten Dominik
2006-10-16  9:01 ` Carsten Dominik
2006-10-16 18:47   ` Richard Stallman
2006-10-17  4:33   ` Nick Roberts [this message]
2006-10-17 10:57     ` Carsten Dominik
2006-10-17 13:13       ` Carsten Dominik
2006-10-17 14:18         ` martin rudalics
2006-10-17 17:49         ` martin rudalics
2006-10-17 21:11           ` Carsten Dominik
2006-10-17 22:03             ` Stefan Monnier
2006-10-17 22:09               ` Lennart Borgman
2006-10-17 22:14                 ` David Kastrup
2006-10-17 22:26                   ` Lennart Borgman
2006-10-17 22:38                     ` David Kastrup
2006-10-17 22:44                       ` Drew Adams
2006-10-17 22:38               ` Carsten Dominik
2006-10-17 22:49                 ` David Kastrup
2006-10-18  4:26                   ` Carsten Dominik
2006-10-18  7:35                     ` David Kastrup
2006-10-20 22:05                       ` Michael Olson
2006-10-21  6:13                         ` David Kastrup
2006-10-21 18:30                           ` Michael Olson
2006-10-23  5:11                             ` Richard Stallman
2006-10-23 13:00                               ` Michael Olson
2006-10-22  0:24                           ` Stefan Monnier
2006-10-22 16:39                             ` David Kastrup
2006-10-18  0:28                 ` Stefan Monnier
2006-10-18  4:26                   ` Carsten Dominik
2006-10-18  4:14             ` Chong Yidong
2006-10-17 18:40       ` Richard Stallman
2006-10-17 20:45         ` martin rudalics
2006-10-18 10:41           ` Richard Stallman
     [not found] <m2lknmthc4.fsf@sl392.st-edmunds.cam.ac.uk>
2006-10-12 16:57 ` Leo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17716.23811.425109.929050@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).