On Thu, 2007-07-19 at 12:29 -0500, Curtis Olson wrote:
> For about 2 weeks now I'm getting a FlightGear crash deep in the OSG
> internals on my laptop.  I was hoping it would be a transient issue in
> OSG and clear itself up, but so far that is not the case.  The same
> code and versions of everything run just fine on my desktop.  I've got
> the most current OSG, SimGear, and FlightGear updated from CVS/SVN
> head.  I've done make clean's just in case some garbage developed in
> my build tree.  I've tried to do all those things I would suggest to
> others if they have some odd thing going on that other people don't
> seem to be seeing. 
> 
> My laptop is a bit older dell latitude with 32Mb Nvidia card.  I am
> running Linux (Fedora Core 6) with the proprietary nvidia drivers.
> Nvidia driver version is 1.0.9631 ... this is the most current version
> that supports my graphics hardware.  The OSG version ran great until a
> few weeks ago.  The plib version continues to run just fine on my
> laptop as it always has.
> 
> FlightGear starts up, shows a splash screen gets as far as showing
> "initializing subsystems".  When I run with --log-level-debug, I see
> that it finishes loading the keyboard  bindings.  Then on the console
> it prints "Splash screen progress setting up time & renderer" although
> this is never drawn.  Immediately after that it crashes trying to call
> sceneView->draw(); 
> 
> Here is the back trace:
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1208727824 (LWP 17599)]
> 0x0075cc4a in osg::GraphicsContext::releaseContext ()
>    from /usr/local/lib/libosg.so.12 
> (gdb) where
> #0  0x0075cc4a in osg::GraphicsContext::releaseContext ()
>    from /usr/local/lib/libosg.so.12
> #1  0x001e1dcf in osgUtil::RenderStage::draw ()
>    from /usr/local/lib/libosgUtil.so.12
> #2  0x001dd5ae in osgUtil::RenderStage::drawPreRenderStages () 
>    from /usr/local/lib/libosgUtil.so.12
> #3  0x001e95a4 in osgUtil::SceneView::draw ()
>    from /usr/local/lib/libosgUtil.so.12
> #4  0x08063c8c in FGRenderer::update (refresh_camera_settings=true)
>     at renderer.cxx :577
> #5  0x08061c6c in FGRenderer::update () at renderer.hxx:41
> #6  0x080a6c41 in fgOSMainLoop () at fg_os_sdl.cxx:249
> #7  0x0805d027 in fgMainInit (argc=2, argv=0xbfdb2294) at
> main.cxx:1071
> #8  0x0805c1aa in main (argc=2, argv=0xbfdb2294) at bootstrap.cxx:220
> 
> This is gdb, so I'm not confident that it has the osg function calls
> correctly identified.
> 
> Does any one have any suggestions or ideas?  It is a problem for me if
> I cannot run FlightGear on my laptop here. :-( 

I have very little knowledge about this, but for more than a month ago
did I have a problem, which looks like this one. It turned out that
RoyVegard also had it.
It had something to do with a null pointer in
src/osgUtil/RenderStage.cpp around line 854 in the OpenSceneGraph source
code.
I got FlightGear working again by using osgViewer instead of SDL.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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

Reply via email to