Dear Konstantin, Sorry, I should have included the code... Here is it. The answer is definitely not inside.
RendererInterface::~RendererInterface() { qDebug("RendererInterface : destroyed"); //Line 119 //Ensure renderThread finishes its execution as it will be deleted (child) /*if(rendererThread->isRunning()) { if(!rendererThread->wait(60000)) { warning("Renderer thread still running - forcing quit"); rendererThread->quit(); if(!rendererThread->wait(60000)) { warning("Renderer thread still running - forcing terminate"); rendererThread->terminate(); } } }*/ } //Line 137 2015-11-09 16:38 GMT+01:00 Konstantin Tokarev <annu...@yandex.ru>: > > > 09.11.2015, 18:22, "Etienne Sandré-Chardonnal" <etienne.san...@m4x.org>: > > Dear all, > > > > I am debugging an app which crashes when an object is being deleted. The > debuggers halt on a segmentation fault inside QObject destructor. The > object deletion was requested by a call to deleteLater() > > > > Here is what I get in the stack trace: > > > > 0 QObject::~QObject qobject.cpp 993 0x7ffff62c7580 > > 1 RendererInterface::~RendererInterface rendererinterface.cpp > 119 0x60664f > > 2 RendererInterface::~RendererInterface rendererinterface.cpp > 137 0x60667e > > 3 qDeleteInEventHandler qobject.cpp 4391 0x7ffff62d06e5 > > > > How is it possible to have the destructor twice in the stack?? At the > beginning I was thinking this was a GDB bug (GDB/MinGW under windows is > buggy) but I get the same result when compiling the app under linux. > > > > Any idea how this can happen? > > Answer is definitely around lines 119-137 of rendererinterface.cpp > > > -- > Regards, > Konstantin >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest