[EMAIL PROTECTED] (Kim F. Storm) writes: > David Kastrup <[EMAIL PROTECTED]> writes: > >> Here is at least the dump, "it" does not seem set to any useful >> value. Probably I should set the breakpoint on abort in order to get >> a useful backtrace. > > I cannot reproduce the crash here. > >> >> Breakpoint 1, abort () at /home/tmp/emacs/src/emacs.c:456 >> 456 kill (getpid (), SIGABRT); >> (gdb) bt >> #0 abort () at /home/tmp/emacs/src/emacs.c:456 >> #1 0x080997b0 in move_it_vertically_backward (it=0xe6c, dy=0) >> at /home/tmp/emacs/src/xdisp.c:6370 > > Could you try to remove the assert in that line, and see if things > work well without it. > > I suspect the two asserts in move_it_vertically_backward are > bogus (although they do appear to be perfectly sane).
I'll try. Anyway, I set the breakpoint on abort as well and tried getting any useful information out of "it". No such luck. Probably the stack frame is not in useful state. Perhaps I need to switch to gcc4 as compiler as that is supposed to output sufficient debug information to let the debugger keep track of variable values even in the presence of optimization. Sigh. I'll give removing the assertion a try. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
