|
Hi Zhihao,
I got the same problem on linux 64bit debug fbxsdk2011.3 .
By debugging the code using valgrind I detected a memory corruption on function fbxsdk_2011_3::KFbxMesh::ComputeComponentMaps.
Here the top of the stack:
==7247== Invalid write of size 4
==7247== at 0x54F554E:
fbxsdk_2011_3::KFbxMesh::ComputeComponentMaps(fbxsdk_2011_3::KFbxMesh::KFbxComponentMap&,
fbxsdk_2011_3::KFbxMesh::KFbxComponentMap&) (in
/usr/local/fbx_20113/lib/gcc4/libfbxsdk_20113_x64.so)
==7247== by 0x54C4190:
fbxsdk_2011_3::KFbxGeometryConverter::ComputePolygonSmoothingFromEdgeSmoothing(fbxsdk_2011_3::KFbxMesh*,
int) const (in /usr/local/fbx_20113/lib/gcc4/libfbxsdk_20113_x64.so)
==7247== by 0x54C5E22:
fbxsdk_2011_3::KFbxGeometryConverter::TriangulateMesh(fbxsdk_2011_3::KFbxMesh
const*) (in /usr/local/fbx_20113/lib/gcc4/libfbxsdk_20113_x64.so)
==7247== by 0x54C609B:
fbxsdk_2011_3::KFbxGeometryConverter::TriangulateInPlace(fbxsdk_2011_3::KFbxNode*)
My guess is that by turning off _SECURE_SCL on windows you are only hiding the problem but the corruption is still there. What do you think?
Thanks for your help,
Emiliano
Author: emilian0
|