On 11.08, Stefan Salewski wrote: > On Mon, 2016-08-08 at 09:16 +0200, Timm Bäder wrote: > > That might be possible of course (especially if your code base does not > > contain a widget that creates its own GdkWindows), but the advice is the > > same for all criticals and warnings you get: Run in gdb with > > G_DEBUG=fatal-warnings or G_DEBUG=fatal-criticals and once you hit the > > one you're interested in, print a backtrace (make sure you have > > GTK+ debugging symbols). > > So I have to recompile all my GTK libs to get debugging symbols? Depends, lots of distributions offer -dev packages with debugging symbols. > I have some hope that that problem may vanish with GTK 3.20 -- but not > too much, because it seems to be never reported to bugzilla. FWIW I can reproduce the issue with 3.20 but not with master. _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list
