Re: Emacs crashes, 07nov16

[David Kastrup]

"Robert J. Chassell" <address@hidden> writes:

>     Do you still get crashes if you use the font ...*iso10646-1 instead of
>     ...*iso8859-1 from the start?
>
> Yes, even with a size of 18, which I did not expect.  
>
> That is in 
> Today's GNU Emacs CVS snapshot, Fri, 2007 Nov 23  11:14 UTC
> GNU Emacs 23.0.50.4 (i686-pc-linux-gnu, GTK+ Version 2.12.1)
> started in debugger with
>
>     set args -i -q \
>     --eval '(emacs-version t)' -bg DodgerBlue4 -fg white \
>     -fn '-misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1' \
>     -geometry 80x44+545+43 -name '-q GNU Emacs in Debugger, font: fixed 18'
>
>
> with the breakpoint at xterm.c:1374 
> and after I evaluated  (x-synchronize t)  in the debuggee
>
> (I could not even visit my test file with a size of 20,
>
>  -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
>
>     #0  0xffffe410 in __kernel_vsyscall ()
>     #1  0xb7483c26 in kill () from /lib/i686/cmov/libc.so.6
>     #2  0x080f906b in abort () at emacs.c:431 
>
> although the only  breakpoint was at xterm.c:1374 

Sigh.  You did compile with -fno-crossjumping?  If you didn't,
tracebacks from noreturn functions like "abort" are quite useless since
the compiler will happily recycle a single abort call for all
opportunities.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum