Guenter Milde wrote:
> Strange:
>
> * I use a released version (LyX 1.6.1 from Debian/unstable)
OK, then it's a real crash, _next_ to the assertion (Richard's backtrace also
indicates a crash).
> * LyX closed down suddenly,
>
> with *.lyx.emergency savings that sometimes where corrupt, :-(
I
On 2009-02-27, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> Is this a known bug that will be fixed in 1.6.2 ?
> BTW note that you faced an assertion, not a crash. In release mode,
> assertions do not shut down LyX.
Strange:
* I use a released version (LyX 1.6.1 from Debian/unstable)
* Ly
Vincent van Ravesteijn - TNW wrote:
As Guenter mentioned, he has a master with childs. Doing a cut and paste
in a child document does crash LyX 1.6.1. I have no current branch or
svn to test with.
OK, now I have it. Note that you get an infinite loop through
emergencyWriteAll() when this hap
Vincent van Ravesteijn - TNW wrote:
> Confirmed.
The assert or the fix?
Jürgen
Vincent van Ravesteijn - TNW wrote:
Whenever I copy/kill and past a branch inset LyX dies with the error message
../../../src/support/lassert.cpp(21): ASSERTION false VIOLATED
IN ../../src/insets/Inset.cpp:137 terminate called after throwing
an instance of 'lyx::support::ExceptionMessage'
> Whenever I copy/kill and past a branch inset LyX dies with the error message
>
>../../../src/support/lassert.cpp(21): ASSERTION false VIOLATED
>IN ../../src/insets/Inset.cpp:137 terminate called after throwing
>an instance of 'lyx::support::ExceptionMessage'
> what(): Inset::buffer_ member n
Guenter Milde wrote:
> Is this a known bug that will be fixed in 1.6.2 ?
Not that I know (although we have fixed many crashes and asserts, so this one
might have been resolved en passant).
In any case, I cannot reproduce with 1.6.3svn (but probably I need a more
detailed recipe).
BTW note that
