Segfault opening cow.obj on Linux

[GoogleCodeExporter]

Hi all!

I have a segfault opening the cow.obj with the OBJImporter... :(

If I open the example and change cow.obj by the zombie obj it work.

This problem doesn't seem to be related to OBJImporter directly but 
cacheAlignmentData()

I suppose this problem is Linux specific. Can someone confirm this?

Program received signal SIGSEGV, Segmentation fault.
0x00007f7953604dde in __gnu_cxx::new_allocator<int>::construct(int*, int 
const&) ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/_coral.so
(gdb) bt
#0  0x00007f7953604dde in __gnu_cxx::new_allocator<int>::construct(int*, int 
const&) ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/_coral.so
#1  0x00007f79536046f8 in std::vector<int, std::allocator<int> >::push_back(int 
const&) ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/_coral.so
#2  0x00007f79537d6292 in coral::Geo::cacheAlignmentData() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/_coral.so
#3  0x00007f79537d5c59 in coral::Geo::cacheFaceNormals() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/_coral.so
#4  0x00007f79537d5ecd in coral::Geo::verticesNormals() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/_coral.so
#5  0x00007f794f5dbe50 in coralUi::GeoDrawNode::updateGeoVBO() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#6  0x00007f794f5dd240 in coralUi::GeoDrawNode::draw() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#7  0x00007f794f5dda1c in coralUi::MainDrawRoutine::drawAll() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#8  0x00007f794f5e8e0e in coralUi::Viewport::draw() ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#9  0x00007f794f5cf3fb in _object* boost::python::detail::invoke<int, void 
(coralUi::Viewport::*)(), boost::python::arg_from_python<coralUi::Viewport&> 
>(boost::python::detail::invoke_tag_<true, true>, int const&, void 
(coralUi::Viewport::*&)(), boost::python::arg_from_python<coralUi::Viewport&>&) 
()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#10 0x00007f794f5cc8cd in boost::python::detail::caller_arity<1u>::impl<void 
(coralUi::Viewport::*)(), boost::python::default_call_policies, 
boost::mpl::vector2<void, coralUi::Viewport&> >::operator()(_object*, _object*) 
()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#11 0x00007f794f5c9713 in 
boost::python::objects::caller_py_function_impl<boost::python::detail::caller<vo
id (coralUi::Viewport::*)(), boost::python::default_call_policies, 
boost::mpl::vector2<void, coralUi::Viewport&> > >::operator()(_object*, 
_object*) ()
   from coral-git-repo/coral/build/coralStandaloneBuild/coral/coralUi/_coralUi.so
#12 0x00007f79542e3edf in boost::python::objects::function::call(_object*, 
_object*) const ()
   from /usr/lib/libboost_python-py26.so.1.46.1
#13 0x00007f79542e4138 in ?? () from /usr/lib/libboost_python-py26.so.1.46.1
#14 0x00007f79542ed283 in 
boost::python::handle_exception_impl(boost::function0<void>) ()
   from /usr/lib/libboost_python-py26.so.1.46.1

Original issue reported on code.google.com by dorian.f...@gmail.com on 12 Feb 2012 at 2:55

[GoogleCodeExporter]

There was another user having issues on linux with some other obj, but on my 
mac it was fine.

I'd suggest investigating in the objLoader code, that should be the only place 
where we can have Os differences...

Original comment by aintergu...@gmail.com on 12 Feb 2012 at 3:28