Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad Error Handling #2

Closed
Microwave89 opened this issue Jul 16, 2015 · 1 comment
Closed

Bad Error Handling #2

Microwave89 opened this issue Jul 16, 2015 · 1 comment

Comments

@Microwave89
Copy link
Owner

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.

@Microwave89
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant