[Interest] Destructor appearing twice in the stack trace?

[Thiago Macieira]

On Monday 09 November 2015 16:21:44 Etienne Sandré-Chardonnal wrote:
> 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?

It depends on what code the compiler generated. It's entirely possible, but I 
can't also rule out a problem.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center