Re: emacs crashed on many OSes (was: emacs crashed on windows-xp)

[Jan Djärv]

Jan Djärv skrev:
> Jason Rumney skrev:
> > > > It crashes with a message print out:
> > > >         Fatal error (11)Segmentation fault
> > > >
> > > > I'm running emacs-unicode-2 (CVS:2006-10-04) in Fedora core 5.
> > > >     
> > >
> > > Doesn't happen for me with CVS trunk on GNU/Linux (redhat 9.0).
> > >   
> >
> > Strange, it does for me on GNU/Linux (Debian testing) as well as 
> > Windows..
>
>
> FWIW, it crashes for me with Mac OSX.


And on FreeBSD 4.11.  Here is a backtrace:

Program received signal SIGSEGV, Segmentation fault.
0x808cea3 in display_count_lines (start=219173, start_byte=219173,
    limit_byte=219583, count=217461, byte_pos_ptr=0xbfbfe710) at xdisp.c:18011
18011                   while (*cursor != '\n' && ++cursor != ceiling_addr)

(gdb) p cursor
$1 = (
    unsigned char *) 0x28635000 <Error reading address 0x28635000: Bad address>
(gdb) where
#0  0x808cea3 in display_count_lines (start=219173, start_byte=219173,
    limit_byte=219583, count=217461, byte_pos_ptr=0xbfbfe710) at xdisp.c:18011
#1  0x808c57d in decode_mode_spec (w=0x86afe00, c=108, field_width=0,
    precision=-3, multibyte=0xbfbfe7b4) at xdisp.c:17769
#2  0x808add6 in display_mode_element (it=0xbfbfe8b0, depth=2, field_width=0,
    precision=-1, elt=141645059, props=137934849, risky=0) at xdisp.c:16906
#3  0x808b274 in display_mode_element (it=0xbfbfe8b0, depth=1, field_width=-1,
    precision=-1, elt=138437181, props=137934849, risky=0) at xdisp.c:17101
#4  0x8078091 in x_consider_frame_title (frame=141225988) at xdisp.c:8994
#5  0x80781ec in prepare_menu_bars () at xdisp.c:9051
#6  0x807b82d in redisplay_internal (preserve_echo_area=0) at xdisp.c:10938
#7  0x807a8cc in redisplay () at xdisp.c:10519
#8  0x8124e79 in read_char (commandflag=1, nmaps=2, maps=0xbfbff538,
    prev_event=137934849, used_mouse_menu=0xbfbff5ec, end_time=0x0)
    at keyboard.c:2633
#9  0x812ea4f in read_key_sequence (keybuf=0xbfbff71c, bufsize=30,
    prompt=137934849, dont_downcase_last=0, can_return_switch_frame=1,
    fix_current_buffer=1) at keyboard.c:8963
#10 0x81226e5 in command_loop_1 () at keyboard.c:1603
#11 0x81a2bf5 in internal_condition_case (bfun=0x81223b4 <command_loop_1>,
    handlers=137999033, hfun=0x8121cf0 <cmd_error>) at eval.c:1481
#12 0x8122080 in command_loop_2 () at keyboard.c:1326
#13 0x81a2678 in internal_catch (tag=137993265,
    func=0x8122060 <command_loop_2>, arg=137934849) at eval.c:1222
#14 0x8122032 in command_loop () at keyboard.c:1305
#15 0x8121a47 in recursive_edit_1 () at keyboard.c:1003
#16 0x8121b97 in Frecursive_edit () at keyboard.c:1064
#17 0x81203e5 in main (argc=4, argv=0xbfbffa40) at emacs.c:1794

(gdb) p ceiling_addr
$2 = (
    unsigned char *) 0x285f7ae5 "\037\nFile: elisp,  Node: Introduction, 
Next: Lisp Data Types,  Prev: Top,  Up: Top\n\n1 Introduction\n", '*' <repeats 
14 times>, "\n\nMost of the GNU Emacs text editor is written in the 
programming\nlanguage called Emacs L"...
(gdb) p cursor
$3 = (
    unsigned char *) 0x28635000 <Error reading address 0x28635000: Bad address>
(gdb) p base
$4 = (
    unsigned char *) 0x2862083c "File: elisp,  Node: Lists,  Next: Sequences 
Arrays Vectors,  Prev: Strings and Characters,  Up: Top\n\n5 
Lists\n*******\n\nA \"list\" represents a sequence of zero or more elements 
(which may be\nany Lisp obj"...
(gdb) p start_byte
$5 = 219173
(gdb) p limit_byte
$6 = 219583
(gdb) p ceiling
$7 = 51917


I'll leave it running in gdb.  If anybody can figure this out or need more 
debugging done,  just let me know.

        Jan D.