Re: Another Crash in Trunk

2008-01-12 Thread Andre Poenitz
On Thu, Jan 10, 2008 at 02:22:52PM -0500, rgheck wrote: > Andre Poenitz wrote: >> On Thu, Jan 10, 2008 at 01:45:23AM -0500, rgheck wrote: >> >>> When lyx2lyx fails with an error: >>> gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet(gdb) quitgdb >>> >> >> Completely unrelated out o

Re: Another Crash in Trunk

2008-01-10 Thread rgheck
Andre Poenitz wrote: On Thu, Jan 10, 2008 at 01:45:23AM -0500, rgheck wrote: When lyx2lyx fails with an error: gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet(gdb) quitgdb Completely unrelated out of interest: Why do you use --interpreter=mi2? It does not give any advantages

Re: Another Crash in Trunk

2008-01-10 Thread Andre Poenitz
On Thu, Jan 10, 2008 at 01:45:23AM -0500, rgheck wrote: > > When lyx2lyx fails with an error: > gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet(gdb) quitgdb Completely unrelated out of interest: Why do you use --interpreter=mi2? It does not give any advantages when used 'manually', does

Re: Another Crash in Trunk

2008-01-09 Thread Abdelrazak Younes
rgheck wrote: When lyx2lyx fails with an error: ... #3 0x0072b269 in lyx::CursorSlice::paragraph (this=optimized out>) at /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/debug/vector:192 It looks like the DocIterator::slices_ is empty and 'DocIterator::top()'

Another Crash in Trunk

2008-01-09 Thread rgheck
When lyx2lyx fails with an error: gdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quiet(gdb) quitgdb /cvs/lyx-devel/trunk/src/lyx --interpreter=mi2 -quietQuit (gdb) quitquit The program is running. Exit anyway? (y or n) [answered Y; input not from terminal] (gdb) Process exited gdb /cvs/