Using a TriMesh results in segfault before space.collide.

Bug #258131 reported by azathothgr
4
Affects Status Importance Assigned to Milestone
pyode (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When a Trimesh geom is added to space, the next space.collide() call segfaults.

Also, when calling getTriangle(index) on any trimesh geom (for any index), the result is an assertion failed error :
python: /build/buildd/ode-0.9.dfsg/GIMPACT/src/gim_trimesh.cpp:183: void gim_trimesh_locks_work_data(GIM_TRIMESH*): Assertion `res==0' failed.

I used this simple tutorial : http://<email address hidden>/msg00049.html
but the only thing I've managed to find is that as soon as the trimesh geom is created, space.collide simply segfaults.

Revision history for this message
Gord Allott (gordallott) wrote :

confirmed on ubuntu hardy 8.04 - pyode 1.2.0-2 - ode 1:0.9.dfsg-1

Changed in pyode:
status: New → Confirmed
Revision history for this message
the trav (the-trav) wrote :

Using the same test code on XP works fine, which may point to a bug in the ode library rather than pyode

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.