Ahhh,
> > Was deleting some text when Lyx crashed. Is the following useful to help
track > > the bug down?
> >
> > #0 0x401e0111 in __kill ()
> > (gdb) q
>
> No, it's not useful. You should have typed "where" to see the call stack.
Is the following better....
(gdb) where
#0 0x401e0111 in __kill ()
#1 0x401dfd66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x401e1447 in abort () at ../sysdeps/generic/abort.c:88
#3 0x8136908 in lyx::abort ()
#4 0x80ad9ab in error_handler ()
#5 <signal handler called>
#6 0x3ffecccc in ?? ()
#7 0x80f00a8 in LyXText::NextBreakPoint ()
#8 0x80f1a44 in LyXText::BreakAgain ()
#9 0x80fa7a9 in LyXText::FullRebreak ()
#10 0x8051f26 in BufferView::update ()
#11 0x8062c70 in LyXView::UpdateTimerCB ()
#12 0x8062c90 in C_LyXView_UpdateTimerCB ()
#13 0x400368bf in fl_object_qread ()
#14 0x40044b8e in fl_check_forms ()
#15 0x80a986d in LyXGUI::runTime ()
#16 0x80aab6b in LyX::LyX ()
#17 0x80ce795 in main ()
#18 0x401d9cb3 in __libc_start_main (main=0x80ce6f0 <main>, argc=9,
argv=0xbffff9c4, init=0x804d718 <_init>, fini=0x814cfc8 <_fini>,
rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff9bc)
at ../sysdeps/generic/libc-start.c:78
(gdb) q
