Re: Gimp 0.99.19 menu weirdness

[Owen Taylor <owt1 cornell edu>]

Owen Taylor <owt1@cornell.edu> writes:

> Daniel Skarda <0rfelyus@atrey.karlin.mff.cuni.cz> writes:
> 
> >   few days ago there were about two mails that complained about
> > strange menu behaviour in new Gimp 0.99.19. I also have been hit by
> > this bug - but it seems that this bug is so rare that no body have
> > replied to those bug reports. Than I asked myself - what did we
> > wrong or sligtly different from the others installing new Gimp? I
> > sought throw mailing list archives but I have not found anything.
> > But - WHOA - that's it: `root@artax:/usr/src/gtk-0.99.4/$ configure
> > --enable-debug=no'. Only few folks bothered to turn off gtk
> > debuging... - and punishment come immediately :)
> 
> Weird. It works if you you compile with the _default_ debug level
> --enable-debug=minimum, but not with --disable-debug.
> 
> The only difference between the two should be that --disable-debug
> turns off all assertion checks.

Which makes perfect sense, when the offending line was:

  g_return_if_fail (gdk_window_get_origin (GTK_WIDGET (menu_item)->window, &tx, &ty));

!!!

(The g_return_if_fail() statements are a "soft" form of assertion -
 that just warn and return)

Regards,
                                        Owen