Re: LyX 1.5 crash while scrolling

[Juergen Spitzmueller]

Georg Baum wrote:
 This smells like a boost thing. Does it happen also if you compile against
 system boost? Do you have that at all? 

No, I haven't installed that currently. Anyway, I think SuSE 10 ships the same 
version than LyX 1.5 (1.33.1).

 Or maybe with the boost directory 
 of 1.4?

How can I compile against that?
What is the procedure anyway? Does it use system boost if it finds it and 
--with-included-boost is not used?

Jürgen

Re: LyX 1.5 crash while scrolling

[Georg Baum]

Juergen Spitzmueller wrote:

 Georg Baum wrote:
 Or maybe with the boost directory
 of 1.4?
 
 How can I compile against that?

I think it would work if you temporarily exchange the boost subdirectory of
LyX with that of 1.4, but I am not sure. Of course you should rerun
autogen.sh etc. and do a full rebuild, because normal file date based
dependency tracking will not work.

 What is the procedure anyway? Does it use system boost if it finds it and
 --with-included-boost is not used?

No, you have to explicitly request --without-included-boost.


Georg

Re: LyX 1.5 crash while scrolling

[Juergen Spitzmueller]

Georg Baum wrote:
> This smells like a boost thing. Does it happen also if you compile against
> system boost? Do you have that at all? 

No, I haven't installed that currently. Anyway, I think SuSE 10 ships the same 
version than LyX 1.5 (1.33.1).

> Or maybe with the boost directory 
> of 1.4?

How can I compile against that?
What is the procedure anyway? Does it use system boost if it finds it and 
--with-included-boost is not used?

Jürgen

Re: LyX 1.5 crash while scrolling

[Georg Baum]

Juergen Spitzmueller wrote:

> Georg Baum wrote:
>> Or maybe with the boost directory
>> of 1.4?
> 
> How can I compile against that?

I think it would work if you temporarily exchange the boost subdirectory of
LyX with that of 1.4, but I am not sure. Of course you should rerun
autogen.sh etc. and do a full rebuild, because normal file date based
dependency tracking will not work.

> What is the procedure anyway? Does it use system boost if it finds it and
> --with-included-boost is not used?

No, you have to explicitly request --without-included-boost.


Georg

LyX 1.5 crash while scrolling

[Juergen Spitzmueller]

1. Load the UserGuide
2. Scroll

= LyX crashes. Not reproducible with 1.4

(preview-latex is disabled)

Jürgen

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1086936672 (LWP 26996)]
lyx::graphics::CacheItem::status (this=0x7) at scoped_ptr.hpp:94
94  BOOST_ASSERT(ptr != 0);

(gdb) bt
#0  lyx::graphics::CacheItem::status (this=0x7) at scoped_ptr.hpp:94
#1  0x08499008 in lyx::graphics::Loader::Impl::statusChanged (this=0x8964860)
at GraphicsLoader.C:260
#2  0x0849a609 in 
boost::detail::function::void_function_obj_invoker0boost::_bi::bind_tvoid, 
boost::_mfi::mf0void, lyx::graphics::Loader::Impl, 
boost::_bi::list1boost::_bi::valuelyx::graphics::Loader::Impl*  , 
void::invoke (function_obj_ptr=
  {obj_ptr = 0x88a99b8, const_obj_ptr = 0x88a99b8, func_ptr = 0x88a99b8, 
data = })
at mem_fn_template.hpp:45
#3  0x0807988a in boost::function0void, std::allocatorvoid ::operator() 
(this=0x8965c34)
at function_template.hpp:576
#4  0x080798c8 in 
boost::operator++boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound0void::callerboost::functionvoid
 
()(), std::allocatorvoid  , 
boost::signals::detail::named_slot_map_iterator, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const, int ([EMAIL PROTECTED]) at 
signal_template.hpp:119
#5  0x08079cf7 in boost::signal0void, boost::last_valuevoid, int, 
std::lessint, boost::functionvoid ()(), std::allocatorvoid  
::operator() (this=0x89658a8) at last_value.hpp:43
#6  0x0848ff12 in lyx::graphics::CacheItem::Impl::setStatus (this=0x8965878,
new_status=lyx::graphics::Converting) at GraphicsCacheItem.C:256
#7  0x08490534 in lyx::graphics::CacheItem::Impl::convertToDisplayFormat 
(this=0x8965878)
at GraphicsCacheItem.C:378
#8  0x084913cf in lyx::graphics::CacheItem::Impl::startLoading 
(this=0x8965878)
at GraphicsCacheItem.C:218
#9  0x0849140a in lyx::graphics::CacheItem::startLoading (this=0x88a8d48)
at GraphicsCacheItem.C:156
#10 0x0849becb in lyx::graphics::LoaderQueue::loadNext (this=0x86858e0) at 
LoaderQueue.C:48
---Type return to continue, or q return to quit---
#11 0x0849d061 in 
boost::detail::function::void_function_obj_invoker0boost::_bi::bind_tvoid, 
boost::_mfi::mf0void, lyx::graphics::LoaderQueue, 
boost::_bi::list1boost::_bi::valuelyx::graphics::LoaderQueue*  , 
void::invoke (function_obj_ptr=
  {obj_ptr = 0x87d0280, const_obj_ptr = 0x87d0280, func_ptr = 0x87d0280, 
data = \200})
at mem_fn_template.hpp:45
#12 0x0807988a in boost::function0void, std::allocatorvoid ::operator() 
(this=0x87d026c)
at function_template.hpp:576
#13 0x080798c8 in 
boost::operator++boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound0void::callerboost::functionvoid
 
()(), std::allocatorvoid  , 
boost::signals::detail::named_slot_map_iterator, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const, int ([EMAIL PROTECTED]) at 
signal_template.hpp:119
#14 0x08079cf7 in boost::signal0void, boost::last_valuevoid, int, 
std::lessint, boost::functionvoid ()(), std::allocatorvoid  
::operator() (this=0x8685928) at last_value.hpp:43
#15 0x083093bd in Timeout::emit (this=0x8685928) at Timeout.C:51
#16 0x08313b1b in qtTimeout::timerEvent (this=0x87d0188) at Timeout.h:72
#17 0x4028c852 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x4022cd41 in QApplication::internalNotify () 
from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x4022d6b9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40221ab8 in QEventLoop::activateTimers () 
from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x401daf4f in QEventLoop::processEvents () 
from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40243c39 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40243b36 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x4022c68f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x08373eeb in lyx_gui::start ([EMAIL PROTECTED], [EMAIL PROTECTED]) at 
lyx_gui.C:248
#26 0x08149563 in LyX::priv_exec (this=0x86bd6c8, [EMAIL PROTECTED], 
argv=0xbfe3a134)

Re: LyX 1.5 crash while scrolling

[Georg Baum]

Am Mittwoch, 22. März 2006 11:24 schrieb Juergen Spitzmueller:
 1. Load the UserGuide
 2. Scroll
 
 = LyX crashes. Not reproducible with 1.4

This smells like a boost thing. Does it happen also if you compile against 
system boost? Do you have that at all? Or maybe with the boost directory 
of 1.4?


Georg

LyX 1.5 crash while scrolling

[Juergen Spitzmueller]

1. Load the UserGuide
2. Scroll

=> LyX crashes. Not reproducible with 1.4

(preview-latex is disabled)

Jürgen

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1086936672 (LWP 26996)]
lyx::graphics::CacheItem::status (this=0x7) at scoped_ptr.hpp:94
94  BOOST_ASSERT(ptr != 0);

(gdb) bt
#0  lyx::graphics::CacheItem::status (this=0x7) at scoped_ptr.hpp:94
#1  0x08499008 in lyx::graphics::Loader::Impl::statusChanged (this=0x8964860)
at GraphicsLoader.C:260
#2  0x0849a609 in 
boost::detail::function::void_function_obj_invoker0, 
boost::_bi::list1 > >, 
void>::invoke (function_obj_ptr=
  {obj_ptr = 0x88a99b8, const_obj_ptr = 0x88a99b8, func_ptr = 0x88a99b8, 
data = ""})
at mem_fn_template.hpp:45
#3  0x0807988a in boost::function0::operator() 
(this=0x8965c34)
at function_template.hpp:576
#4  0x080798c8 in 
boost::operator++ >, 
boost::signals::detail::named_slot_map_iterator>, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const&, int> ([EMAIL PROTECTED]) at 
signal_template.hpp:119
#5  0x08079cf7 in boost::signal0 
>::operator() (this=0x89658a8) at last_value.hpp:43
#6  0x0848ff12 in lyx::graphics::CacheItem::Impl::setStatus (this=0x8965878,
new_status=lyx::graphics::Converting) at GraphicsCacheItem.C:256
#7  0x08490534 in lyx::graphics::CacheItem::Impl::convertToDisplayFormat 
(this=0x8965878)
at GraphicsCacheItem.C:378
#8  0x084913cf in lyx::graphics::CacheItem::Impl::startLoading 
(this=0x8965878)
at GraphicsCacheItem.C:218
#9  0x0849140a in lyx::graphics::CacheItem::startLoading (this=0x88a8d48)
at GraphicsCacheItem.C:156
#10 0x0849becb in lyx::graphics::LoaderQueue::loadNext (this=0x86858e0) at 
LoaderQueue.C:48
---Type  to continue, or q  to quit---
#11 0x0849d061 in 
boost::detail::function::void_function_obj_invoker0, 
boost::_bi::list1 > >, 
void>::invoke (function_obj_ptr=
  {obj_ptr = 0x87d0280, const_obj_ptr = 0x87d0280, func_ptr = 0x87d0280, 
data = "\200"})
at mem_fn_template.hpp:45
#12 0x0807988a in boost::function0::operator() 
(this=0x87d026c)
at function_template.hpp:576
#13 0x080798c8 in 
boost::operator++ >, 
boost::signals::detail::named_slot_map_iterator>, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const&, int> ([EMAIL PROTECTED]) at 
signal_template.hpp:119
#14 0x08079cf7 in boost::signal0 
>::operator() (this=0x8685928) at last_value.hpp:43
#15 0x083093bd in Timeout::emit (this=0x8685928) at Timeout.C:51
#16 0x08313b1b in qtTimeout::timerEvent (this=0x87d0188) at Timeout.h:72
#17 0x4028c852 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x4022cd41 in QApplication::internalNotify () 
from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x4022d6b9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40221ab8 in QEventLoop::activateTimers () 
from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x401daf4f in QEventLoop::processEvents () 
from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40243c39 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40243b36 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x4022c68f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x08373eeb in lyx_gui::start ([EMAIL PROTECTED], [EMAIL PROTECTED]) at 
lyx_gui.C:248
#26 0x08149563 in LyX::priv_exec (this=0x86bd6c8, [EMAIL PROTECTED], 
argv=0xbfe3a134)

Re: LyX 1.5 crash while scrolling

[Georg Baum]

Am Mittwoch, 22. März 2006 11:24 schrieb Juergen Spitzmueller:
> 1. Load the UserGuide
> 2. Scroll
> 
> => LyX crashes. Not reproducible with 1.4

This smells like a boost thing. Does it happen also if you compile against 
system boost? Do you have that at all? Or maybe with the boost directory 
of 1.4?


Georg