查看单个帖子
旧 2009-05-06, 04:22 PM   #1
yang686526
高级会员
 
注册日期: 06-11
帖子: 14579
精华: 1
现金: 224494 标准币
资产: 234494 标准币
yang686526 向着好的方向发展
默认 【转帖】is this a bug

is this a bug?
is this a bug?
when i wblocked dimension's entity, it is crash that invoking oduninitialize();
is there any way to fix it?
thanks!
before calling oduninitialize you must destroy all oddb* objects.
they may be "alive" if some smart pointer is still pointing to them.
be sure that all smart pointers went out of scope (destroyed) or assign null to them.
sergey slezkin
quote:
originally posted by sslezkin
before calling oduninitialize you must destroy all oddb* objects.
they may be "alive" if some smart pointer is still pointing to them.
be sure that all smart pointers went out of scope (destroyed) or assign null to them.
thanks, i just destoryed the oddbdatabaseptr object before calling oduninitialize, and all the oddb* objects belong to the oddbdatabaseptr object. if there are not dimension objects, it works fine.
is it possible to reproduce in our 2.6.3 samples? for example in odamfcapp?
note, where is excustobjs sample which implements a number of commands which can be executed in odamfcapp including tests for wblock functionality.
look at _wblockclone_func() in drxdebugcmds.cpp
sergey slezkin
yang686526离线中   回复时引用此帖
GDT自动化论坛(仅游客可见)