![]() |
【转帖】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_aecscheduledata:oaction(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 |
所有的时间均为北京时间。 现在的时间是 08:21 PM. |