* Melchior FRANZ -- Thursday 26 July 2007: > Yes. That looks very much like an OSG bug. And valgrind agrees.
I have to take this back. The code is rather ugly -- it reads more data than are available, and valgrind complains about that. But after that the line decoder breaks correctly. I don't see memory corruption here. Now, if I could reproduce the problem ... > BTW: according to my checker we don't have a single corrupted SGI > image file in CVS. And I have to take this back, too. At least partly. What we have in CVS is files where RLE data packages aren't correctly closed with a zero. Normally readers check for that (OSG does), so it's not a big problem. But it's a violation of the SGI spec. Probably another one of the GIMP bugs. And then they claim that "aggressive RLE" isn't supported on SGI. Yeah, sure. Maybe it's just the corrupted GIMP files that aren't supported? :-} m. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
