Bennett Helm wrote:
On Jul 16, 2007, at 11:45 AM, Abdelrazak Younes wrote:
Bennett Helm wrote:
I'm using pdfsync via lyxpipe to have LyX jump to where I click in
the .pdf file of an open LyX document. Recently I've been getting
crashes. Here's the console output:
Assertion triggered in void lyx::Text::setCursorIntern(lyx::Cursor&,
lyx::pit_type, lyx::pos_type, bool, bool) by failing check "this ==
cur.text()" in file Text2.cpp:746
Is there more info I should provide?
A backtrace :-)
How's this? --
Assertion triggered in void lyx::Text::setCursorIntern(lyx::Cursor&,
lyx::pit_type, lyx::pos_type, bool, bool) by failing check "this ==
cur.text()" in file Text2.cpp:746
Could you please verify that your cursor was not within an inset before
using pdfsync? Could you also try to reproduce the crash when the cursor
is in the _main_ text? If you cannot, then I might be able to cure this bug.
Some more question below:
Program received signal SIGABRT, Aborted.
0x9003d66c in kill ()
(gdb) bt
#0 0x9003d66c in kill ()
#1 0x9010e8cf in raise ()
#2 0x9010d422 in abort ()
#3 0x000ec0ad in lyx::support::abort () at abort.cpp:25
#4 0x000c7c74 in lyx::Text::setCursorIntern (this=0xf10737c,
[EMAIL PROTECTED], par=708, pos=0, setfont=true, boundary=false) at
Text2.cpp:746
#5 0x000c7d1a in lyx::Text::setCursor (this=0xf10737c, [EMAIL PROTECTED],
par=708, pos=0, setfont=1, boundary=0) at Text2.cpp:714
Could you verify that paragraph number 708 exists? If it doesn't then we
have a problem with TexRow::getIdFromRow(). I remember that Alfredo had
a patch concerning this TexRow class but I cannot remember the bug number.
#6 0x00025d1d in lyx::BufferView::setCursorFromRow (this=0xe9d1530,
row=11812) at BufferView.cpp:1265
Ouch... row=11812! Is the document that big?
#7 0x0008615e in lyx::LyXFunc::dispatch (this=0xe91cd60,
[EMAIL PROTECTED]) at LyXFunc.cpp:1261
#8 0x00096e06 in lyx::Server::callback (serv=0xe9bfda0,
[EMAIL PROTECTED]) at Server.cpp:464
#9 0x000963e8 in lyx::LyXComm::read_ready (this=0xe9bfdd0) at
Server.cpp:268
#10 0x007d5b7b in boost::_bi::bind_t<void, boost::_mfi::mf0<void,
lyx::LyXComm>, boost::_bi::list1<boost::_bi::value<lyx::LyXComm*> >
>::operator() (this=0xe9fb0e0) at ../boost/boost/bind/bind_template.hpp:20
#11 0x0077529b in boost::function0<void, std::allocator<void>
>::operator() (this=0xe9fb0dc) at
../boost/boost/function/function_template.hpp:692
#12 0x00218ec2 in lyx::socket_callback::qt_metacall (this=0xe9fb0d0,
_c=InvokeMetaMethod, _id=4, _a=0xbfffe9c8) at socket_callback.cpp:30
The information below seems bogus... I have difficulty to understand the
backtrace at this point... Was the cursor inset an equation before the
crash?
#13 0x0023015a in QMetaObject::activate () at QLImage.cpp:173
#14 0x00609989 in QSocketNotifier::activated () at fileiter.cpp:214
#15 0x003c017c in QSocketNotifier::event () at cregex.cpp:428
#16 0x001c7d18 in QApplicationPrivate::notify_helper () at
MathParser.cpp:1472
#17 0x001cbac9 in QApplication::notify () at MathParser.cpp:1472
Abdel.
