Hans Fugal wrote: > It may not be the same problem, but I remember getting almost no > helpful indications from either of those debug methods so OTOH it may > indeed be the same problem. Make sure you don't have conflicting > plugins in /Library or wherever the OSG release readme says to put > them, try moving them from /usr/local to /usr, try setting some > environment variable that I wish I had written down, etc.
After checking the system again I'm confident that the *only* OSG is in /usr/local/lib. And again, all the osgexamples as well as my other OSG projects are fine. > One way to be sure is to see if you can tell if this is the first > texture that it's trying to load. My guess is yes, but if it's not I put a breakpoint on applyTexImage2D_load and it picked up the following textures being loaded: - Splash1... - wxecho.rgb - cirrus.rgba *BANG* So it's not the first but awfully close. The first one obviously is the splash screen which I can see. No idea about the second one. The third one gives the segfault. Is there anything exciting happening before the environment is initialized? > then it's not the same problem. Also, if you built OSG from scratch > maybe you didn't get all the plugins needed by flightgear? Don't think so, I can open the texture using 'osgviewer --image cirrus.rgba' Lost a sea, /ulrich ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel