Murray Cumming wrote: > > > Hi, > > > > I have problems with custom exception handling. Whenever i add a > > custom handler using Glib::add_exception_handler(), even a direct > > copy of standard glibmm_unexpected_exception(), I get this: > > > > terminate called without an active exception > > Aborted > > > > Apparently, I shouldn't rethrow the current exception, but then > > there is no way to know what it is... Any ideas? Is it a known > > problem? > > > > (But Gtkmm is very old, version 2.4.10 in Debian Sarge.) > > Maybe you could post a small example.
Sorry for the false alarm. I discovered that this is caused by compiler mixing (GCC 3.3 and 4.0.) Apparently, warning about possible libstdc++ conflict is there on purpose :) Looks like I'll have to abandon GCC 4.0 while I'm using Gtkmm (pre)compiled with GCC 3.3. Paul _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
