> Not trying to be offensive, but if I could reproduce this every time, > I wouldn't be asking for debugging suggestions.
Oh, sorry. I assume you have verified that you don't have any heap corruption by running the code under valgrind on Linux? Other than that I really can't give any specific advice. Perhaps ask somebody else to read the code carefully. If the problem did not occur at some earlier stage, then you could do a binary search through your version history to find the exact changes that made the problems occur. But if the problem happens very randomly and rarely, of course that is going to be tedious, as you can never be sure if one version really is clean, or if the problem just happens not to occur when you test that version. --tml _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
