From: mustafap <mpa...@gm...> - 2008-07-16 18:38:06
|
Hi, I recently installed gazebo (finally:D) and tried the examples but there was a segmentation fault. There are different faults at different examples but some examples are working. There seems to be a problem with iface. trimesh.world and factory.world files do work but other have errors. I am giving the fault of pioneer2dx.world: [server/GazeboConfig.cc:68] Gazebo Path[/usr/local/share/gazebo] [server/GazeboConfig.cc:76] Ogre Path[/usr/lib/OGRE] creating /tmp/gazebo-mustafa-0 creating /tmp/gazebo-mustafa-0/simulation.default 112 704 creating /tmp/gazebo-mustafa-0/position.position_iface_0 112 224 creating /tmp/gazebo-mustafa-0/laser.laser_iface_0 112 12440 creating /tmp/gazebo-mustafa-0/fiducial.fiducial_iface_0 112 20928 Segmentation fault Others have similar faults which end with ...._iface_. Thank you -- View this message in context: http://www.nabble.com/segmentation-fault-tp18493933p18493933.html Sent from the playerstage-gazebo mailing list archive at Nabble.com. |
From: Benjamin K. <ben...@gm...> - 2008-07-16 18:51:02
|
Hard to say what causes it. Please make a backtrace: 1. run "gdb gazebo" (preferrably from the directories the world files are in) 2. type "run bandit.world" (or some other world file that is not working) 3. Watch gazebo crash and then type "bt" send the output to this mailing list :-) |
From: mustafap <mpa...@gm...> - 2008-07-16 19:01:24
|
Ok, this is after I ran pioneer2dx.world: [server/GazeboConfig.cc:68] Gazebo Path[/usr/local/share/gazebo] [server/GazeboConfig.cc:76] Ogre Path[/usr/lib/OGRE] [New Thread 0xb7f45ab0 (LWP 2417)] creating /tmp/gazebo-mustafa-0 creating /tmp/gazebo-mustafa-0/simulation.default 112 704 creating /tmp/gazebo-mustafa-0/position.position_iface_0 112 224 creating /tmp/gazebo-mustafa-0/laser.laser_iface_0 112 12440 creating /tmp/gazebo-mustafa-0/fiducial.fiducial_iface_0 112 20928 Program received signal SIGSEGV, Segmentation fault. 0x036f8742 in ?? () from /usr/lib/dri/libdricore.so and this is the result of 'bt': #0 0x036f8742 in ?? () from /usr/lib/dri/libdricore.so #1 0x036f9000 in vbo_split_copy () from /usr/lib/dri/libdricore.so #2 0x036f8552 in vbo_split_prims () from /usr/lib/dri/libdricore.so #3 0x036fecee in _tnl_draw_prims () from /usr/lib/dri/libdricore.so #4 0x036f7267 in ?? () from /usr/lib/dri/libdricore.so #5 0x036f7457 in ?? () from /usr/lib/dri/libdricore.so #6 0x00f834b8 in ?? () from /usr/lib/OGRE/RenderSystem_GL.so #7 0x0284da11 in Ogre::SceneManager::renderSingleObject () from /usr/lib/libOgreMain-1.4.7.so #8 0x028427d1 in Ogre::SceneManager::SceneMgrQueuedRenderableVisitor::visit () from /usr/lib/libOgreMain-1.4.7.so #9 0x028113d4 in Ogre::QueuedRenderableCollection::acceptVisitorGrouped () from /usr/lib/libOgreMain-1.4.7.so #10 0x02811a41 in Ogre::QueuedRenderableCollection::acceptVisitor () from /usr/lib/libOgreMain-1.4.7.so #11 0x02844df1 in Ogre::SceneManager::renderObjects () from /usr/lib/libOgreMain-1.4.7.so #12 0x02847c54 in Ogre::SceneManager::renderAdditiveStencilShadowedQueueGroupObjects () from /usr/lib/libOgreMain-1.4.7.so #13 0x02844694 in Ogre::SceneManager::_renderQueueGroupObjects () from /usr/lib/libOgreMain-1.4.7.so #14 0x02845685 in Ogre::SceneManager::renderVisibleObjectsDefaultSequence () from /usr/lib/libOgreMain-1.4.7.so #15 0x0284581f in Ogre::SceneManager::_renderVisibleObjects () from /usr/lib/libOgreMain-1.4.7.so #16 0x08aac13d in Ogre::TerrainSceneManager::_renderVisibleObjects () from /usr/lib/OGRE/Plugin_OctreeSceneManager.so #17 0x02845dd5 in Ogre::SceneManager::_renderScene () from /usr/lib/libOgreMain-1.4.7.so #18 0x08aac276 in Ogre::TerrainSceneManager::_renderScene () from /usr/lib/OGRE/Plugin_OctreeSceneManager.so #19 0x026b955e in Ogre::Camera::_renderScene () from /usr/lib/libOgreMain-1.4.7.so #20 0x028c1f80 in Ogre::Viewport::update () from /usr/lib/libOgreMain-1.4.7.so #21 0x0281b58d in Ogre::RenderTarget::update () from /usr/lib/libOgreMain-1.4.7.so #22 0x0281f8b9 in Ogre::RenderWindow::update () from /usr/lib/libOgreMain-1.4.7.so #23 0x0281f83c in Ogre::RenderWindow::update () from /usr/lib/libOgreMain-1.4.7.so #24 0x080cad00 in gazebo::OgreAdaptor::UpdateWindow (this=0x9f80f60, window=0xa4b4ce8, camera=0xa4b4b48) at server/rendering/OgreAdaptor.cc:456 #25 0x080e6586 in gazebo::UserCamera::Update (this=0xa4b4b48) at server/rendering/UserCamera.cc:86 #26 0x08104ee3 in gazebo::GLWindow::Update (this=0xa2918c0) at server/gui/GLWindow.cc:148 #27 0x0810a2ef in gazebo::GLFrame::Update (this=0x9fb1ec8) at server/gui/GLFrame.cc:134 #28 0x08107fa4 in gazebo::GLFrameManager::Update (this=0x9fb1aa0) at server/gui/GLFrameManager.cc:151 #29 0x081039a4 in gazebo::Gui::Update (this=0x9fa8d88) at server/gui/Gui.cc:113 #30 0x08128944 in gazebo::Simulator::MainLoop (this=0x9f78560) at server/Simulator.cc:289 #31 0x0810db36 in main (argc=Cannot access memory at address 0xc ) at server/main.cc:293 mustafap wrote: > > Hi, > I recently installed gazebo (finally:D) and tried the examples but there > was a segmentation fault. There are different faults at different examples > but some examples are working. There seems to be a problem with iface. > trimesh.world and factory.world files do work but other have errors. I am > giving the fault of pioneer2dx.world: > > [server/GazeboConfig.cc:68] > Gazebo Path[/usr/local/share/gazebo] > [server/GazeboConfig.cc:76] > Ogre Path[/usr/lib/OGRE] > creating /tmp/gazebo-mustafa-0 > creating /tmp/gazebo-mustafa-0/simulation.default 112 704 > creating /tmp/gazebo-mustafa-0/position.position_iface_0 112 224 > creating /tmp/gazebo-mustafa-0/laser.laser_iface_0 112 12440 > creating /tmp/gazebo-mustafa-0/fiducial.fiducial_iface_0 112 20928 > Segmentation fault > > Others have similar faults which end with ...._iface_. > > Thank you > -- View this message in context: http://www.nabble.com/segmentation-fault-tp18493933p18494367.html Sent from the playerstage-gazebo mailing list archive at Nabble.com. |
From: Benjamin K. <ben...@gm...> - 2008-07-16 19:10:32
|
Hi, looks like an issue with either Ogre or your graphics driver. Run "glxinfo | grep direct". If you see something like "direct rendering: no", you will have to look for new drivers for your graphics card. Otherwise, you could try compiling the Ogre demos and see whether they work (not sure how exactly to do this though, there should be instructions included with Ogre). Good luck, Ben |
From: mustafap <mpa...@gm...> - 2008-07-16 19:50:46
|
Direct rendering is yes and I installed a game named chess which workes with ogre and it workes fine. My ogre version is 1.4.7 so I will try to install the latest one 1.4.9. thanks Benjamin Kloster wrote: > > Hi, > looks like an issue with either Ogre or your graphics driver. Run > "glxinfo | grep direct". If you see something like "direct rendering: > no", you will have to look for new drivers for your graphics card. > Otherwise, you could try compiling the Ogre demos and see whether they > work (not sure how exactly to do this though, there should be > instructions included with Ogre). > > Good luck, > Ben > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Playerstage-gazebo mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo > > -- View this message in context: http://www.nabble.com/segmentation-fault-tp18493933p18495317.html Sent from the playerstage-gazebo mailing list archive at Nabble.com. |
From: mustafap <mpa...@gm...> - 2008-07-17 12:05:52
|
Hi, I upgraded ogre but nothing chanced. Are you sure this error is caused by ogre or direct rendering? There are other programs that have the same error "argc=Cannot access memory at address 0xc". mustafap wrote: > > Direct rendering is yes and I installed a game named chess which workes > with ogre and it workes fine. My ogre version is 1.4.7 so I will try to > install the latest one 1.4.9. > thanks > > > Benjamin Kloster wrote: >> >> Hi, >> looks like an issue with either Ogre or your graphics driver. Run >> "glxinfo | grep direct". If you see something like "direct rendering: >> no", you will have to look for new drivers for your graphics card. >> Otherwise, you could try compiling the Ogre demos and see whether they >> work (not sure how exactly to do this though, there should be >> instructions included with Ogre). >> >> Good luck, >> Ben >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Playerstage-gazebo mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo >> >> > > -- View this message in context: http://www.nabble.com/segmentation-fault-tp18493933p18506958.html Sent from the playerstage-gazebo mailing list archive at Nabble.com. |
From: Benjamin K. <ben...@gm...> - 2008-07-17 13:23:45
|
Hello again, I'm quite sure. The error you mention ("cannot access memory...") is very generic and can have a multitude of origins. But the backtrace you posted earlier definitely points towards the graphic. You can see this from the line starting with "#0", the error originated from libdricore.so. DRI is the Direct Rendering Infrastructure, and libdricore.so is its corresponding library file. Unfortunately, I'm out of ideas. Depending on your graphics card, you could try using an alternate graphics driver, another graphics card (or even computer), change the linux distro or any combination of these. I'm sorry. Maybe someone else has another, more feasible idea. Ben -- Psssst! Schon das coole Video vom GMX MultiMessenger gesehen? Der Eine für Alle: http://www.gmx.net/de/go/messenger03 |
From: mustafap <mpa...@gm...> - 2008-07-17 13:47:04
|
Ok. I will try to find another graphic card and try it from there thank you. Benjamin Kloster wrote: > > Hello again, > I'm quite sure. The error you mention ("cannot access memory...") is very > generic and can have a multitude of origins. But the backtrace you posted > earlier definitely points towards the graphic. You can see this from the > line starting with "#0", the error originated from libdricore.so. DRI is > the Direct Rendering Infrastructure, and libdricore.so is its > corresponding library file. > > Unfortunately, I'm out of ideas. Depending on your graphics card, you > could try using an alternate graphics driver, another graphics card (or > even computer), change the linux distro or any combination of these. I'm > sorry. > > Maybe someone else has another, more feasible idea. > > Ben > -- > Psssst! Schon das coole Video vom GMX MultiMessenger gesehen? > Der Eine für Alle: http://www.gmx.net/de/go/messenger03 > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Playerstage-gazebo mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo > > -- View this message in context: http://www.nabble.com/segmentation-fault-tp18493933p18508832.html Sent from the playerstage-gazebo mailing list archive at Nabble.com. |