On Sat, Jan 30, 2010 at 12:34 PM, Tommaso Cucinotta wrote:
> Tommaso Cucinotta wrote:
>
>> Hi,
>>
>> start LyX, C-n, C-w ==> assertion (LyXFunc.cpp:537).
>>
> Another way: start LyX, choose Tools->Preferences, same assertion.
>
> lassert.cpp(21): ASSERTION bv VIOLATED IN LyXFunc.cpp:537
>
> T.
Tommaso Cucinotta wrote:
Hi,
start LyX, C-n, C-w ==> assertion (LyXFunc.cpp:537).
Another way: start LyX, choose Tools->Preferences, same assertion.
lassert.cpp(21): ASSERTION bv VIOLATED IN LyXFunc.cpp:537
T.
Hi,
start LyX, C-n, C-w ==> assertion (LyXFunc.cpp:537).
lyx svn, r33266, Linux
(gdb) bt
#0 0x757634b5 in *__GI_raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x75766f50 in *__GI_abort () at abort.c:92
#2 0x005b65c8 in lyx::lyx_exit (exit_code=3786) a
On Jan 4, 2007, at 7:39 AM, Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Looking at the backtrace, it seems that a resize event is
Abdelrazak> triggered just after the doGreyOut() method is initiated
Abdelrazak>
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Looking at the backtrace, it seems that a resize event is
Abdelrazak> triggered just after the doGreyOut() method is initiated
Abdelrazak> and before it is finished, hence the crash. Now the
Ab
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Looking at the backtrace, it seems that a resize event is
Abdelrazak> triggered just after the doGreyOut() method is initiated
Abdelrazak> and before it is finished, hence the crash. Now the
Ab
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Looking at the backtrace, it seems that a resize event is
Abdelrazak> triggered just after the doGreyOut() method is initiated
Abdelrazak> and before it is finished, hence the crash. Now the
Abdelrazak> question is why
On Jan 3, 2007, at 6:30 PM, Abdelrazak Younes wrote:
Bennett Helm wrote:
In recent 1.5svn: start LyX, open a file, close it. LyX crashes.
Here's the backtrace:
QPixmap::operator=: Cannot assign to pixmap during painting
QCoreGraphicsPaintEngine::begin: Painter already active
QPainter::begin()
Bennett Helm wrote:
In recent 1.5svn: start LyX, open a file, close it. LyX crashes. Here's
the backtrace:
QPixmap::operator=: Cannot assign to pixmap during painting
QCoreGraphicsPaintEngine::begin: Painter already active
QPainter::begin(): Returned false
Does this patch solves the crash?
A
Bennett Helm wrote:
In recent 1.5svn: start LyX, open a file, close it. LyX crashes. Here's
the backtrace:
QPixmap::operator=: Cannot assign to pixmap during painting
QCoreGraphicsPaintEngine::begin: Painter already active
QPainter::begin(): Returned false
Looking at the backtrace, it seems t
In recent 1.5svn: start LyX, open a file, close it. LyX crashes.
Here's the backtrace:
QPixmap::operator=: Cannot assign to pixmap during painting
QCoreGraphicsPaintEngine::begin: Painter already active
QPainter::begin(): Returned false
Program received signal EXC_BAD_ACCESS, Could not access
1.5.0-alpha crashes on closing a buffer on Intel Mac.
Recipe: Start LyX. File > New; File > Close. Here's the backtrace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x
0x001d0505 in QFont::QFont () at QLImage.C:172
172
12 matches
Mail list logo
