You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If any handled error occurs execution soon ends up in mydie() which terminates the program.
Much better would be to decide what to do or reset for an error to be continuable again and
not to break execution. Such a smart error handling is supposed to let one analyze different image files in the same execution.
The text was updated successfully, but these errors were encountered:
This issue has been addressed now:
As long as everything is resetted properly, no further actions are needed
and the loop can run over and over, again.
As soon as an error occurs which would lead to a handle or memory leak,
the error is displayed and the program is terminated.
However, if defcreator can't open an imagefile (e.g. STATUS_INVALID_IMAGE_FORMAT) the program simply displays this error and execution will start over again,
since no memory or handles are about to be leaked then.
If any handled error occurs execution soon ends up in mydie() which terminates the program.
Much better would be to decide what to do or reset for an error to be continuable again and
not to break execution. Such a smart error handling is supposed to let one analyze different image files in the same execution.
The text was updated successfully, but these errors were encountered: