More info on the segfault in the gtk_text_buffer widget:
installed the Debian package libgtk2.0-dbg, set
LD_LIBRARY_PATH=/usr/lib/debug and GTK_DEBUG=text (but I'm not sure if the
Debian package was compiled with --enable-debug=yes) and ran my program in
the debugger:
Program received signal SIGSEGV, Segmentation fault.
_gtk_text_line_previous_could_contain_tag (line=0x80924d8, tree=0x8090f80,
tag=0x808afc8) at gtktextbtree.c:4341
4341 gtktextbtree.c: No such file or directory.
in gtktextbtree.c
bt
#0 _gtk_text_line_previous_could_contain_tag (line=0x80924d8,
tree=0x8090f80, tag=0x808afc8) at gtktextbtree.c:4341
#1 0x40130597 in gtk_text_iter_backward_to_tag_toggle (iter=0xbfffdad4,
tag=0x808afc8) at gtktextiter.c:4021
#2 0x0804b550 in doc_highlight_line (doc=0x808b088) at highlight5.c:772
#3 0x0804ba93 in buffer_insert_text_lcb (textbuffer=0x808b700,
iter=0xbfffe0e4, string=0x81444e0 " ", len=1, doc=0x808b088)
at highlight5.c:890
I also looked a bit at the code in gvd (gnu visual debugger - a front end
for gdb) and noticed this happens:
in gtktextbtree.c line 4339 line_ancestor_parent is set to NULL
on line 4341 node is set to line_ancestor_parent->children
and that creates the segfault
is this already a bit more helpful?
regards,
Olivier
Attachment:
pgpindf54KCdj.pgp
Description: PGP signature