Re: [bug]org-mode with flyspell-mode freezes emacs

[Carsten Dominik]

Apologies for my previous message in which I said I could not reproduce 
this error under gdb.  This was a mistake on my side, caused by an 
alias expansion of the command emacs that make "gdb emacs" refer to 
emacs 21 instead of Emacs 22.

Anyway, I do now have a backtrace for this problem.  Can anyone extract 
something useful from this?

Thanks.

- Carsten



(gdb) run -l test test.org
Starting program: /Users/dominik/bin/ne -l test test.org
Reading symbols for shared libraries ++++. done
^C
Program received signal SIGINT, Interrupt.
0x00157454 in validate_interval_range (object=20860132, 
begin=0xbfffd8e8, end=0xbfffd8e8, force=0) at textprop.c:135
135       CHECK_NUMBER_COERCE_MARKER (*end);
(gdb) backtrace
#0  0x00157454 in validate_interval_range (object=20860132, 
begin=0xbfffd8e8, end=0xbfffd8e8, force=0) at textprop.c:135
#1  0x001573c4 in validate_interval_range (object=20860132, 
begin=0xbfffd8e8, end=0xbfffd8e8, force=0) at textprop.c:129
#2  0x00158274 in Ftext_properties_at (position=432, object=20860128) 
at textprop.c:590
#3  0x0015830c in Fget_text_property (position=432, prop=-1073751832, 
object=-1073751832) at textprop.c:611
#4  0x0015a7b0 in text_property_stickiness (prop=58879617, pos=0, 
buffer=20860132) at textprop.c:1789
#5  0x00156284 in adjust_for_invis_intang (pos=20860132, test_offs=0, 
adj=20860132, test_intang=2729760) at intervals.c:1989
#6  0x00156540 in set_point_both (buffer=0x13e4ce4, charpos=20860128, 
bytepos=20860132) at intervals.c:2112
#7  0x000e8558 in search_command (string=28183443, bound=432, 
noerror=58720825, count=0, direction=0, RE=0, posix=0) at search.c:1008
#8  0x00114d54 in Ffuncall (nargs=432, args=0x1) at eval.c:3003
#9  0x00142110 in Fbyte_code (bytestr=17315416, vector=1, maxdepth=1) 
at bytecode.c:679
#10 0x001152e8 in funcall_lambda (fun=1, nargs=0, arg_vector=0x3800239) 
at eval.c:3180
#11 0x00114e88 in Ffuncall (nargs=432, args=0x1) at eval.c:3050
#12 0x00142110 in Fbyte_code (bytestr=17315416, vector=1, maxdepth=1) 
at bytecode.c:679
#13 0x001152e8 in funcall_lambda (fun=1, nargs=0, arg_vector=0x3800239) 
at eval.c:3180
#14 0x00114e88 in Ffuncall (nargs=432, args=0x1) at eval.c:3050
#15 0x00142110 in Fbyte_code (bytestr=17315416, vector=1, maxdepth=1) 
at bytecode.c:679
#16 0x001152e8 in funcall_lambda (fun=1, nargs=0, arg_vector=0x3800239) 
at eval.c:3180
#17 0x00114e88 in Ffuncall (nargs=432, args=0x1) at eval.c:3050
#18 0x00114604 in run_hook_with_args (nargs=0, args=0x1, cond=28183443) 
at eval.c:2652
#19 0x00114410 in Frun_hooks (nargs=432, args=0x1b0) at eval.c:2515
#20 0x00114d18 in Ffuncall (nargs=432, args=0x38109e1) at eval.c:2996
#21 0x00114850 in call1 (fn=432, arg1=432) at eval.c:2774
#22 0x00112860 in internal_condition_case (bfun=0xa9040 
<safe_run_hooks_1>, handlers=58720825, hfun=0xa9080 
<safe_run_hooks_error>) at eval.c:1477
#23 0x000a9160 in safe_run_hooks (hook=432) at keyboard.c:2131
#24 0x000a8584 in command_loop_1 () at keyboard.c:1875
#25 0x00112860 in internal_condition_case (bfun=0xa7364 
<command_loop_1>, handlers=58767017, hfun=0xa6a84 <cmd_error>) at 
eval.c:1477
#26 0x000a6f48 in command_loop_2 () at keyboard.c:1326
#27 0x00112218 in internal_catch (tag=432, func=0xa6f08 
<command_loop_2>, arg=58720777) at eval.c:1218
#28 0x000a6ea0 in command_loop () at keyboard.c:1305
#29 0x000a66c0 in recursive_edit_1 () at keyboard.c:1003
#30 0x000a6878 in Frecursive_edit () at keyboard.c:1064
#31 0x000a52e0 in main (argc=1601296, argv=0x2d0210) at emacs.c:1794




On Oct 15, 2006, at 6:20, Richard Stallman wrote:

>     On Thu Oct 12 10:51:51 2006 +0100, Carsten Dominik wrote:
>
>     I can reproduce this under Emacs 22, but I have not been able to
>     figure out what is causing this, because Emacs hangs so that it 
> cannot
>     even be stopped with C-g.
>
>     It seems to be caused by links which contain hidden and intangible 
> text.
>
>     Don't really know where to go from here.
>
>     - Carsten
>
>
> Can you run Emacs under GDB, stop it while it is in this loop,
> and send us the backtrace?
>
> As a next step, you could follow the advice in etc/DEBUG about
> investigating an infinite loop.  This information could probably enable
> someone else to debug the Emacs bug.
>
> For others' information, the initial bug report:
>
> From: Leo <address@hidden>
>
>     Starting emacs with "emacs -q -l test test.org". Then press "C-x
>     ]". Emacs will freeze.
>
>     "test" and "test.org" are attached.
>
>     Tested on GNU Emacs 23.0.0.1 (i686-pc-linux-gnu, GTK+ Version 
> 2.8.20)
>     of 2006-10-04 running under fedora core 5.
>
>
> (setq inhibit-startup-message t)
> (add-hook 'text-mode-hook
>           (lambda nil
>             (flyspell-mode t)))
> (add-to-list 'auto-mode-alist '("\\.org" . org-mode))

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477