Re: Segfault in current bzr

[Eli Zaretskii]

> From: Lars Magne Ingebrigtsen <address@hidden>
> Date: Mon, 27 Sep 2010 21:56:49 +0200
> 
> I've now managed to kill Emacs twice.  It happened while I was reading a
> picture-heavy news group.
> 
> Here's what gdb said in the backtrace:
> 
> #0  0x00007ffff1e11457 in kill () from /lib/libc.so.6
> #1  0x00000000004ebc25 in abort () at emacs.c:427
> #2  0x00000000005a5dd9 in wait_reading_process_output (
>     time_limit=<value optimized out>, microsecs=<value optimized out>, 
>     read_kbd=-1, do_display=<value optimized out>, 
>     wait_for_cell=<value optimized out>, wait_proc=0x0, just_wait_proc=0)
>     at process.c:5072
> #3  0x0000000000418434 in sit_for (timeout=120, reading=1, do_display=1)
>     at dispnew.c:6107
> #4  0x00000000004fc2f9 in read_char (commandflag=<value optimized out>, 
>     nmaps=<value optimized out>, maps=<value optimized out>, 
>     prev_event=<value optimized out>, used_mouse_menu=<value optimized out>, 
>     end_time=<value optimized out>) at keyboard.c:2811
> #5  0x00000000004fd4d9 in read_key_sequence (keybuf=<value optimized out>, 
>     bufsize=<value optimized out>, prompt=<value optimized out>, 
>     dont_downcase_last=<value optimized out>, 
>     can_return_switch_frame=<value optimized out>, 
>     fix_current_buffer=<value optimized out>) at keyboard.c:9339
> #6  0x00000000004ffa60 in command_loop_1 () at keyboard.c:1618

Looks really similar to what Thierry Volpiatto reported earlier today.

> Any ideas?

I'd suspect something in the latest changes by Jan.  The last change
is the first suspect, right?