Re: crash after save [master]

Le 31/01/2018 à 18:15, Pavel Sanda a écrit : Pavel Sanda wrote: Jean-Marc Lasgouttes wrote: I cannot reproduce, but here is a candidate patch for fixing Cursor::sanitize. Please test. I have done other changes for enforcing encapsulation between CursorData and Cursor. I can confirm that the

Re: crash after save [master]

Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > I cannot reproduce, but here is a candidate patch for fixing > > Cursor::sanitize. > > > > Please test. I have done other changes for enforcing encapsulation between > > CursorData and Cursor. > > I can confirm that the crash is gone. Pavel

Re: crash after save [master]

Jean-Marc Lasgouttes wrote: > I cannot reproduce, but here is a candidate patch for fixing > Cursor::sanitize. > > Please test. I have done other changes for enforcing encapsulation between > CursorData and Cursor. I can confirm that the crash is gone. Pavel

Re: crash after save [master]

Le 14/01/2018 à 19:42, Pavel Sanda a écrit : Pavel Sanda wrote: Still trying. Bisect leads to: commit 02028c0b12ba94093e4e77494e7158a58f1631e5 Author: Jean-Marc Lasgouttes Date: Sun Jul 23 18:13:33 2017 +0200 Move some Cursor methods to CursorData I cannot

Re: crash after save [master]

Le 14 janvier 2018 19:42:19 GMT+01:00, Pavel Sanda a écrit : >Pavel Sanda wrote: >> Still trying. > >Bisect leads to: > >commit 02028c0b12ba94093e4e77494e7158a58f1631e5 >Author: Jean-Marc Lasgouttes >Date: Sun Jul 23 18:13:33 2017 +0200 > >Move some

Re: crash after save [master]

Am Sonntag, den 14.01.2018, 19:42 +0100 schrieb Pavel Sanda: > Pavel Sanda wrote: > > Still trying. > > Bisect leads to: > > commit 02028c0b12ba94093e4e77494e7158a58f1631e5 > Author: Jean-Marc Lasgouttes > Date: Sun Jul 23 18:13:33 2017 +0200 Here, too. Jürgen

Re: crash after save [master]

Pavel Sanda wrote: > Still trying. Bisect leads to: commit 02028c0b12ba94093e4e77494e7158a58f1631e5 Author: Jean-Marc Lasgouttes Date: Sun Jul 23 18:13:33 2017 +0200 Move some Cursor methods to CursorData Basically, everything that does not depend on a

Re: crash after save [master]

Am Sonntag, den 14.01.2018, 19:01 +0100 schrieb Pavel Sanda: > That's a difficult one. It seems not reproducible when > completely new configs are created (~/.lyx). > (Reconfigure does not help to the situation though.) > > And using the old ones is difficult due to bug > which is already fixed

Re: crash after save [master]

Jürgen Spitzmüller wrote: > Am Sonntag, den 14.01.2018, 14:14 +0100 schrieb Pavel Sanda: > > Hi, > > aynone can reproduce this? > > 1. launch lyx, new file > > 2. insert program listing, put few chars into the inset > > 3. ctrl+s to save , save to it to eg. /tmp/aaa.lyx > > 4. kaboom > > Yes (in

Re: crash after save [master]

Am Sonntag, 14. Januar 2018 um 14:14:30, schrieb Pavel Sanda > Hi, > aynone can reproduce this? > 1. launch lyx, new file > 2. insert program listing, put few chars into the inset > 3. ctrl+s to save , save to it to eg. /tmp/aaa.lyx > 4. kaboom Same with qt5 here. > I can't get

Re: crash after save [master]

Am Sonntag, den 14.01.2018, 14:14 +0100 schrieb Pavel Sanda: > Hi, > aynone can reproduce this? > 1. launch lyx, new file > 2. insert program listing, put few chars into the inset > 3. ctrl+s to save , save to it to eg. /tmp/aaa.lyx > 4. kaboom Yes (in master, not in 2.3.x). > I can't get

crash after save [master]

Hi, aynone can reproduce this? 1. launch lyx, new file 2. insert program listing, put few chars into the inset 3. ctrl+s to save , save to it to eg. /tmp/aaa.lyx 4. kaboom I can't get reasonable backtrace. Master & qt4. Pavel