On Wed, Sep 19, 2012 at 4:09 AM, Jean-Marc Lasgouttes
wrote:
> Le 19/09/2012 09:46, Scott Kostyshak a écrit :
>
>> I tried to reproduce the Valgrind error (on commit 7a7b9abf1) as an
>> exercise and I could not. Here is my Valgrind log:
>> http://paste.debian.net/190784/
>> Note that I did not spe
Le 19/09/2012 09:46, Scott Kostyshak a écrit :
I tried to reproduce the Valgrind error (on commit 7a7b9abf1) as an
exercise and I could not. Here is my Valgrind log:
http://paste.debian.net/190784/
Note that I did not specify any options.
I see nothing that refers to KeyChecker or to around GuiAp
On Mon, Sep 10, 2012 at 6:06 AM, Jean-Marc Lasgouttes
wrote:
> Le 10/09/2012 02:12, Scott Kostyshak a écrit :
>
>> On Sun, Sep 9, 2012 at 7:50 PM, Tommaso Cucinotta wrote:
>>
>>> Now I did, and it doesn't crash any more. Still, I'm very puzzled by the
>>> *why* initializing that boolean should ha
On 11/09/12 04:34, Scott Kostyshak wrote:
I just committed a patch that should make that message disappear.
Please let me know if you keep seeing it. Scott
I can't see it any more, thanks.
T.
On Sun, Sep 9, 2012 at 7:50 PM, Tommaso Cucinotta wrote:
> On 09/09/12 02:54, LyX Ticket Tracker wrote:
>>
>> I have not been able to reproduce since JMarc's fix. Have you tried on
>> updated trunk?
>
>
> Now I did, and it doesn't crash any more. Still, I'm very puzzled by the
> *why* initiali
Le 10/09/2012 02:12, Scott Kostyshak a écrit :
On Sun, Sep 9, 2012 at 7:50 PM, Tommaso Cucinotta wrote:
Now I did, and it doesn't crash any more. Still, I'm very puzzled by the
*why* initializing that boolean should have fixed the crash.
I would be interested in the answer to this also.
Be
On Sun, Sep 9, 2012 at 7:50 PM, Tommaso Cucinotta wrote:
> Now I did, and it doesn't crash any more. Still, I'm very puzzled by the
> *why* initializing that boolean should have fixed the crash.
I would be interested in the answer to this also.
> Without too much philosophy, another possibly re
On 09/09/12 02:54, LyX Ticket Tracker wrote:
I have not been able to reproduce since JMarc's fix. Have you tried on
updated trunk?
Now I did, and it doesn't crash any more. Still, I'm very puzzled by the
*why* initializing that boolean should have fixed the crash.
Without too much philos