GNOME Bugzilla – Bug 348912
Broken libatkmm lib with 2.6.10 release
Last modified: 2006-08-02 16:49:36 UTC
Regexxer crashes with 2.6.10, in libatkmm.so: Starting program: /usr/bin/regexxer Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x8eb000 [Thread debugging using libthread_db enabled] [New Thread -1208465728 (LWP 31494)] (regexxer:31494): glibmm-WARNING **: failed to wrap type of 'AtkNoOpObject' (regexxer:31494): glibmm-WARNING **: failed to wrap type of 'AtkNoOpObject' Program received signal SIGSEGV, Segmentation fault.
+ Trace 69684
Thread NaN (LWP 31494)
287 stop_button_->set_sensitive(false); 288 stop_button_->signal_clicked().connect(signal_cancel_clicked.make_slot()); 289 290 progressbar_->set_pulse_step(0.025); 291 292 stop_button_->get_accessible()->set_description(_("Cancels the running search")); 293 294 show_all_children(); 295 } 296
libatkmm was not being initialized. gtkmm 2.6.13 should fix this (and hopefully not introduce other bugs). Please test and confirm. My apologies again.
I'm sorry but I am still seeing the same segfault with regexxer. :-( Calling get_accessible() on a GTK component still returns a NULL reference.
Hmm, that change doesn't actually seem to have made it into the tarball. Please try this one. It seems OK with regexxer in my tests: http://www.murrayc.com/temp/gtkmm-2.6.14.tar.gz If it's OK then I'll release it. We'll get this done eventually.
Excellent, this fixes it, and I verified ABI compatibility with all current gtkmm-based application in Fedora. Ship it I say.
Done.