Ulrich Hertlein wrote: > > A stack trace is usually helpful, as it would tell you where (in what > function) the crash > occurred. To that effect, it does not need to be interactive. > > As Stephan already said, any additional information is helpful (your original > mail didn't > have a lot of that).
This is good to know for the next time I run into a problem, thanks. > Maybe the QT reader is buggy in the stream-reading path. This seems to have been the case. I set up the ReaderWriterPNG class to directly include libpng and libz in its own source (not a clean solution, but for relatively small libraries like that it seemed easier than mucking about with include/link directory settings in 3 different IDEs), and added support for the "istreampng" file extension, so that I had an easy way to make sure it superceded any of the default plugins that (claim to) support reading a png from stream. It seems to be working at the moment, but if anyone has suggestions for a less hacky solution, that would be appreciated. ~Thomas ------------------------ Vermont Sustainable Heating Initiative (http://www.sustainableheatingvt.org) || Village2Village Project (http://www.village2villageproject.org) ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=32637#32637 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
