As I reported recently, I'm running fgfs through the valgrind debugger. Due to hundreds of error messages and to still having to learn valgrind I'm not very productive yet. I did "resolve" a few hundred error messages, though, all of which were caused by only a few (sort of) cosmetic bugs. In most cases it was code like this:
char *s = new char[10]; ... delete s; // should be: delete [] s; which causes a "mismatched free/delete/delete []" error message. Memory that was allocated as a vector is not properly destroyed with "delete []". If the used data type doesn't have a destructor, it shouldn't be a problem. But it's simply not correct and a potential source for serious problems. This is why this gets consequently fixed in KDE. Will patches to fix these in fgfs be accepted, or is it not considered a bug at all? In any case, when working with valgrind I =have= to deal with it. There has at least to be a "suppression" rule for every such C++ violation. I've already added some entries in my plib.supp file, because the plib developers don't seem to be keen to fix it. (And they have a lot of such sloppy code.) BTW: one real bug was already fixed in plib thanks to my valgrind tests on fgfs. :-) m. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
