On Sat, 2009-02-07 at 14:25 -0500, Matthew Talbert wrote: > > 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 > > I still think maybe we're missing each other here. The problem has > never occurred on linux, and the software has run there for several > years, so heap corruption seems unlikely. The problem occurs only on > Windows, and only with the libwimp theme engine. We don't have any > previous versions that worked correctly as this is our first porting > attempt. > It still may be worth your time to run it through valgrind on linux. Just because it works fine doesn't mean your program has no memory usage bugs. If it does, changing platforms is exactly the kind of thing that would make such an error present itself.
-Larry <la...@yrral.net> _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
