In the hope that I could get some useful information about the
mysterious crashes of LyX-1.1.4 that have troubled me and other users,
I've been running a session inside gdb. It froze today, in what I
believe was the equivalent of the mystery crashes. At the time I was
repeating some key press. Here is the stack trace:
(gdb) run
Starting program: /usr/local/bin/lyx
In MapColor [flcolor.c 807] ColormapFull. Using subsititutions
Program received signal SIGSEGV, Segmentation fault.
0xd6cec in LyXText::RedoParagraphs (this=0x244cf8, cur=@0xffff9649,
endpar=0x2a31e8) at text2.C:837
837 && tmprow->previous->par == first_phys_par) {
(gdb) where
#0 0xd6cec in LyXText::RedoParagraphs (this=0x244cf8, cur=@0xffff9649,
endpar=0x2a31e8) at text2.C:837
#1 0xd990c in LyXText::CutSelection (this=0x244cf8, doclear=true)
at text2.C:2026
#2 0xd10cc in LyXText::DeleteLineForward (this=0x244cf8) at text.C:2877
#3 0x9f724 in LyXFunc::Dispatch (this=0x1efc40, ac=125,
do_not_use_this_arg=0x1bb9e0 "") at lyxfunc.C:1680
#4 0x9a2e4 in LyXFunc::processKeyEvent (this=0x1efc40, ev=0xef7a61b4)
at lyxfunc.C:287
#5 0x582d0 in LyXView::KeyPressMask_raw_callback (fl=0x1ec3f0, xev=0xef7a61b4)
at LyXView.C:362
#6 0x583a8 in C_LyXView_KeyPressMask_raw_callback (fl=0x1ec3f0,
xev=0xef7a61b4) at LyXView.C:395
#7 0xef737fac in do_interaction_step ()
#8 0xef738a48 in fl_treat_interaction_events ()
#9 0xef738a98 in fl_check_forms ()
#10 0x8ec9c in LyXGUI::runTime (this=0x11ac00) at lyx_gui.C:635
#11 0x8ffa4 in LyX::LyX (this=0xeffff3e8, argc=0xeffff47c, argv=0xeffff49c)
at ../src/lyx_main.C:129
#12 0xac760 in main (argc=1, argv=0xeffff49c) at ../src/main.C:43
(gdb)
This is LyX-1.1.4fix2, on sparc-solaris-2.6, gcc-2.8.1, xforms-0.88.
If there is other information I can supply that would be useful for
debugging, please let me know what I should try. Regards, and good
luck to the developers in unraveling this.
--
Ronald Florence http://members.home.net/18james
