Georg Baum wrote: > Am Donnerstag, 16. November 2006 12:41 schrieb Peter Kümmel: >> Bennett Helm wrote: >>> 1.5.0 alpha crashes every time on quit on Intel Mac. Here's the > backtrace: >>> Program received signal SIGABRT, Aborted. >>> 0x9003d1dc in kill () >>> (gdb) bt >>> #0 0x9003d1dc in kill () >>> #1 0x9010f2af in raise () >>> #2 0x9010de02 in abort () >>> #3 0x90b4039c in __gnu_cxx::__verbose_terminate_handler () >>> #4 0x90b3e602 in __gxx_personality_v0 () >>> #5 0x90b3e640 in std::terminate () >>> #6 0x90b3ea93 in __cxa_pure_virtual () >> Maybe it is a variation of this problem: >> >> "You probably already know that this error is caused by calling pure >> virtual methods from the constructor or destructor of the base class. >> It must be an indirect call, because GCC will issue an error about >> direct calls. " > > Can you please explain how that could be possible? We don't create an > Application object (this is not possible because Application contains pure > virtual methods). We create an GuiApplication object only, and that does > not have pure virtual methods.
OK, wrong Ansatz. > I suspect that this is again a problem of destruction oder: > LyXComm::endPipe calls theApp->unregisterSocketCallback when theApp is > already destructed. I am not going to dig further into this matter > anymore, I already helped to solve this problem at least two times, and > that is enough. Sorry for not having fixed a bug which I've not introduced. Regards, Peter
