On 22/11/2008 20:41, Enrico Forestieri wrote:
On Sat, Nov 22, 2008 at 07:23:56PM +0100, Abdelrazak Younes wrote:
Actually the internal buffer is properly created and deleted; IOW I
cannot reproduce the assertion... Do you still can?
The bug does not always happens. Here is a recipe f
Enrico Forestieri wrote:
On Sat, Nov 22, 2008 at 07:23:56PM +0100, Abdelrazak Younes wrote:
Actually the internal buffer is properly created and deleted; IOW I
cannot reproduce the assertion... Do you still can?
The bug does not always happens. Here is a recipe for triggering it:
1) Lo
On Sat, Nov 22, 2008 at 07:23:56PM +0100, Abdelrazak Younes wrote:
> Actually the internal buffer is properly created and deleted; IOW I
> cannot reproduce the assertion... Do you still can?
The bug does not always happens. Here is a recipe for triggering it:
1) Load and preview the user guide (D
On 22/11/2008 14:58, Abdelrazak Younes wrote:
On 22/11/2008 14:44, rgheck wrote:
Jürgen Spitzmüller wrote:
rgheck wrote:
I think the warning is wrong, though. There's no reason there
should be
a failure to remove the temporary directory...except perhaps that
it was
already destroyed. So I th
On 22/11/2008 14:44, rgheck wrote:
Jürgen Spitzmüller wrote:
rgheck wrote:
I think the warning is wrong, though. There's no reason there should be
a failure to remove the temporary directory...except perhaps that it
was
already destroyed. So I think we have an extra Buffer lying around for
so
Jürgen Spitzmüller wrote:
rgheck wrote:
I think the warning is wrong, though. There's no reason there should be
a failure to remove the temporary directory...except perhaps that it was
already destroyed. So I think we have an extra Buffer lying around for
some reason, and it's being destroyed
rgheck wrote:
> I think the warning is wrong, though. There's no reason there should be
> a failure to remove the temporary directory...except perhaps that it was
> already destroyed. So I think we have an extra Buffer lying around for
> some reason, and it's being destroyed on exit. This might be
Jürgen Spitzmüller wrote:
Vincent van Ravesteijn - TNW wrote:
#0 0x00606de8 in lyx::emergencyCleanup () at LyX.cpp:799
#1 0x00607115 in lyx::lyx_exit (exit_code=1) at LyX.cpp:196
#2 0x0076b80e in boost::assertion_failed (expr=0xe191b6
"false", function=0xf6b
Vincent van Ravesteijn - TNW wrote:
> >#0 0x00606de8 in lyx::emergencyCleanup () at LyX.cpp:799
> >#1 0x00607115 in lyx::lyx_exit (exit_code=1) at LyX.cpp:196
> >#2 0x0076b80e in boost::assertion_failed (expr=0xe191b6
>
> "false", function=0xf6bfe0 "void >lyx::doAssert(co
Vincent van Ravesteijn - TNW wrote:
-Original Message-
From: Richard Heck [mailto:[EMAIL PROTECTED]
#0 0x00606de8 in lyx::emergencyCleanup () at LyX.cpp:799
#1 0x00607115 in lyx::lyx_exit (exit_code=1) at LyX.cpp:196
#2 0x0076b80e in boost::assertion_fa
-Original Message-
From: Richard Heck [mailto:[EMAIL PROTECTED]
>#0 0x00606de8 in lyx::emergencyCleanup () at LyX.cpp:799
>#1 0x00607115 in lyx::lyx_exit (exit_code=1) at LyX.cpp:196
>#2 0x0076b80e in boost::assertion_failed (expr=0xe191b6
"false", function=0
#0 0x00606de8 in lyx::emergencyCleanup () at LyX.cpp:799
#1 0x00607115 in lyx::lyx_exit (exit_code=1) at LyX.cpp:196
#2 0x0076b80e in boost::assertion_failed (expr=0xe191b6
"false", function=0xf6bfe0 "void lyx::doAssert(const char*, const char*,
long int)", file=0xf6bf
12 matches
Mail list logo
