Emacs crashes. It prompts with a question to attach gdb to debug. Not much more, sorry to say. I'm not used to gdb though, so getting a trace for the error was to big a task a.t.m.
This should be reproducible in windows using the same emacs-version though. So I'll make sure to send a mail to emacs-devel. Regards Gustav On Thu, Dec 22, 2011 at 6:13 PM, Nick Dokos <nicholas.do...@hp.com> wrote: > Nicolas Goaziou <n.goaz...@gmail.com> wrote: > > > Gustav Wikström <gustav.e...@gmail.com> writes: > > > > > Yes, unfortunately it also breaks with "-q". Using > "toggle-debug-on-error" > > > does not work since emacs fails. It's not reporting any error before > this > > > failure. > > > > > > I've tried to debug what happens with "debug-on-entry" when calling > > > "org-cycle". What I find is that after a call to "overlay-put" the > program > > > breaks. > > > > > > I've also tried the same procedure without enabling > "org-startup-indented" > > > and then nothing bad happens. This single change in emacs -q results > in the > > > reported behaviour for me. > > > > > > Nicolas, are you using windows and emacs 24.0.92? > > > > No, I'm using GNU/Linux and Emacs 24.0.92. > > > > Anyway, if emacs crashes, whatever may be the badness of Org indent > > code, the problem should be reported to the emacs devel mailing list > > instead: all that we may come up with here would be a hack. > > > > > > FWIW, I cannot reproduce it either (GNU Emacs 24.0.90.2 > (x86_64-unknown-linux-gnu, GTK+ Version 2.22.0) of 2011-10-27 and > Org-mode version 7.8.02 (release_7.8.02.2.g490d6a)) so the Windoze part > seems essential. > > I'm not sure how much of a development environment the OP has set up on > his box, but if gdb is available, running emacs under gdb and getting a > stacktrace to report to the emacs devel list seems like the best route > forward. > > BTW, is there no error message at all? emacs just dies? > > Nick > >
