ds27680
18-06-2010, 07:51 PM
applies to dwgConvert 6.0 A.05
It would seem at some point under certain circumstances dwgconvert calls the CRT function _chdrive with 0 as parameter. _chdrive checks the parameter internally for validity extract from cRT sources:
if (drive < 1 || drive > 26) {
_doserrno = ERROR_INVALID_DRIVE;
_VALIDATE_RETURN(("Invalid Drive Index",0), EACCES, -1);
}
this calls out in the end the _invalid_parameter default handler which results in the process being terminated.
I was unable to find a reliable way to reproduce the issue, sometimes it occurs after a few conversions, sometimes I cannot reproduce it. it would seem not to be related to a certain file type /content since sometimes it works with the same file that caused problems before.
Unfortunately I did not save the stack when the issue occurred and for the time being I am unable to reproduce the issue.
It would seem at some point under certain circumstances dwgconvert calls the CRT function _chdrive with 0 as parameter. _chdrive checks the parameter internally for validity extract from cRT sources:
if (drive < 1 || drive > 26) {
_doserrno = ERROR_INVALID_DRIVE;
_VALIDATE_RETURN(("Invalid Drive Index",0), EACCES, -1);
}
this calls out in the end the _invalid_parameter default handler which results in the process being terminated.
I was unable to find a reliable way to reproduce the issue, sometimes it occurs after a few conversions, sometimes I cannot reproduce it. it would seem not to be related to a certain file type /content since sometimes it works with the same file that caused problems before.
Unfortunately I did not save the stack when the issue occurred and for the time being I am unable to reproduce the issue.