what does exception ewasopenforwrite indicate?
what does exception ewasopenforwrite indicate?
during a save of a dwg that is created from scratch i get the following exception:
first-chance exception at 0x7c81eb33 in utldxf_d.exe: microsoft c++ exception: oderror_wasopenforwrite @ 0x0012ea70.
first-chance exception at 0x7c81eb33 in utldxf_d.exe: microsoft c++ exception: oderror @ 0x0012ecac.
unhandled exception at 0x7c81eb33 in utldxf_d.exe: microsoft c++ exception: oderror @ 0x0012ecac.
in errordefs.h i find:
od_error_def( ewasopenforwrite, "was open for write")
what have i typically done wrong?
the write call is:
odwrfilebuf
hfilebuff(sadfilename);
pdxfdb->writefile(&hfilebuff, kdwg, kdhl_1015);
the toolkit version is 1.12 for .net 2003.
-rune jorgensen
www.dds.no
this exception means that you have a smart pointer pointing to some object in database being written to file.
then the last smart pointer pointing to a object goes out of scope the object gets closed. at this moment some actions are performed to keep database integrity. if an object was not closed invalid file can be saved. so we throw the exception if object being saved to file was modified and was not closed.
to fix the situation you can rearrange your code in such manner that smart pointers go out of scope before saving the file - their destructors will release pointed objects.
or you can assign null to the pointers.
sergey slezkin
is there any aid i can get in the debugger? the object id of the object that has smartpointers still locked on it? class of the object? access to something like:
oderror_wasopenforwrite::getobjectid()
-rune
-rune jorgensen
www.dds.no
if you have no dd sources and setting in vc debug/exceptions/microsoft c++ exceptions = stop always
does not work for you try the following:
code:
catch(oderror_wasopenforwrite& err)
{
oddbobjectid id = err.getobjectid();
oddbhandle h = id.handle();
oddbobjectptr pobj = id.openobject();
odstring strclassname = pobj->isa().name();
}
sergey slezkin
the compiler could not find the declaration of oderror_wasopenforwrite and neither could i. but i managed to hack my way to the data by making oderror::m_pcontext public and the oderrorcontextwithid members public.
and indeed, the offending smartpointer was found.
-rune
-rune jorgensen
www.dds.no
i have this very same problem, is there a better way than the "hacked"?
it seems to be a problem only when writing to dwg, not dxf!
- jesper
another way is:
code:
catch(oderror& err)
{
// this string will contain handle of opened object
odstring strdesc = err.description();
}
sergey slezkin
hello,
rune jørgensen, could you tell me, how you meneged to get oderrorcontextwithid object?
best regards,
andrey.
this was solved in 2004 so i may not recall all the details.
if your problem is to find the id of the object that is not released, then try:
#include "dberrorwasopenforwrite.h"
and try the first suggestion from sergey.
if you want to access the oderrorcontextwithid object, then i have no other recolletion of that other than what i posted back then: making oderror::m_pcontext public and the oderrorcontextwithid members public. m_pcontext points to oderrorcontextwithid on such an exception.
kind regards,
-rune jorgensen
thank you for your answer.
i just have resolved my problem.
i try to create an empty oddbpolyline entity (it havn't any vertex) and add to a base.
i didn't sift an incorect input data.
when library write a file, it generete the exception "outofmemory".
it apparent only in the 2.6.3 ver.
it was a very big file and very small polyline :-)
goodbye.
andrey