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

odunitialize causes access violation
odunitialize causes access violation
with attached drawing, odunitialize causes an access violation in the following location :
opendwg_issue! aecpecontainer_aecscheduledataaction(enum aecpecontainer_aecscheduledata::action) + 2755 bytes
opendwg_issue! odrxdynamiclinkerimpl::unregmodule(class odrxmodule *) + 206 bytes
the code i use to re-produce is as follows :
void doload() {
odrx_init_static_module_map();
{
oddbdatabaseptr dwgdb = dwgsvcs.readfile( "p:\\05a303-$_w06135.dwg", true, false, oda::ksharedenyno );
}
}
while(1) {
:dinitialize(&dwgsvcs);
:drxinitwinntcrypt();
{
doload();
}
:drxuninitwinntcrypt();
:duninitialize();
}
then if i ever try and load same drawing, it causes an unknown exception in readfile.
this may actually be a adtdirect bug. but i thought i would start with dddirect forum first.
also version i am using is 2.3.0.
cheers
jason
attached files
in dd 2.3.1 a bug was fixed which caused crash if odinitialize() - odunitialize() are called multiple times.
it took effect if freetype library is used (non-windows configurations and borland).
sergey slezkin
it looks more like adt bug
vladimir
quote:
originally posted by sergey slezkin
in dd 2.3.1 a bug was fixed which caused crash if odinitialize() - odunitialize() are called multiple times.
it took effect if freetype library is used (non-windows configurations and borland).
this is on a windows build. so therefore is unlikely this is the case.
cheers
jason
quote:
originally posted by wvk
it looks more like adt bug
i suspected as such, due to the crash is in aecschedule, i will submit to adt forum.
cheers
jason
yang686526离线中   回复时引用此帖
GDT自动化论坛(仅游客可见)