Re: compiling gtkmm with atkmm support fails in implementor.cc

[Kjell Ahlstedt <kjell ahlstedt bredband net>]

A crash in the Atk::Implementor's destructor is surprising. It's empty, and there are no data in Atk::Implementor. The same holds for its base class Glib::Interface. And Glib::Interface's base class Glib::ObjectBase is a virtual base class. Its destructor shall not be called from Glib::Interface's destructor. Thus, Atk::Implementor's destructor should be practically a noop (no operation).

Have you built atkmm with the same compiler as gtkmm? And with compatible compiler options?

Kjell

Den 2015-11-15 kl. 16:27, skrev codekiddy:

Hello there!

Just want to hear if anyone had the same problem as me...

Gtkmm can be compiled with or without atkmm support, and in my case compiling without atkmm works just fine,

but if I set  #define GTKMM_ATKMM_ENABLED when building gtkmm, then gtkmm applications will fail on run-time.

when closing an app, it will break in implementor.cc Implementor::~Implementor() noexcept {}  (atkmm source file).

Building with msvc-140, it does not matter which atkmm version I use, gtkmm apps always crash when closing them.

This is not the case and everything works fine if I do not define GTKMM_ATKMM_ENABLED during gtkmm compilation process.

Please give any advice on how to debug this problem.

Thank you so much!