Bug#548350: The segfault is still there

Rémi Vanicat vanicat at debian.org
Sun Sep 27 00:23:05 UTC 2009


I can confirm the bug in 0.22.1. Here is a bactatrace with symbol and
lxterminal. I've a very similar bacttrace with roxterm.

Program received signal SIGSEGV, Segmentation fault..
0xb7f3d9df in _vte_terminal_ring_append (terminal=0x810b908, fill=0)
at /home/moi/src-system/libvte/vte-0.22.1/./src/vte.c:306
306             return _vte_terminal_ring_insert (terminal,
_vte_ring_next (terminal->pvt->screen->row_data), fill);
(gdb) bt
#0  0xb7f3d9df in _vte_terminal_ring_append (terminal=0x810b908,
fill=0) at /home/moi/src-system/libvte/vte-0.22.1/./src/vte.c:306
#1  0xb7f5f8e3 in vte_sequence_handler_cd (terminal=0x810b800, params=0x0)
    at /home/moi/src-system/libvte/vte-0.22.1/./src/vteseq.c:1063
#2  0xb7f5ffbe in vte_sequence_handler_erase_in_display
(terminal=0x810b800, params=0x80cfe70)
    at /home/moi/src-system/libvte/vte-0.22.1/./src/vteseq.c:2658
#3  0xb7f60a21 in _vte_terminal_handle_sequence (terminal=0x810b800,
match_s=0x8119d68 "erase-in-display", match=1056,
    params=0x80cfe70) at
/home/moi/src-system/libvte/vte-0.22.1/./src/vteseq.c:3293
#4  0xb7f500d0 in vte_terminal_process_incoming (terminal=0x810b800)
at /home/moi/src-system/libvte/vte-0.22.1/./src/vte.c:3763
#5  0xb7f5086a in time_process_incoming (terminal=0x810b800) at
/home/moi/src-system/libvte/vte-0.22.1/./src/vte.c:13971
#6  0xb7f50e78 in process_timeout (data=0x0) at
/home/moi/src-system/libvte/vte-0.22.1/./src/vte.c:14018
#7  0xb7793556 in ?? () from /lib/libglib-2.0.so.0
#8  0xb7792e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#9  0xb7796623 in ?? () from /lib/libglib-2.0.so.0
#10 0xb7796aea in g_main_loop_run () from /lib/libglib-2.0.so.0
#11 0xb7c9ce19 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x0804f332 in ?? ()
#13 0xb75f67a5 in __libc_start_main () from /lib/i686/cmov/libc.so.6
#14 0x0804c841 in ?? ()






More information about the pkg-gnome-maintainers mailing list