-
Notifications
You must be signed in to change notification settings - Fork 277
Cleanup error handling elf reader #2955
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
Cleanup error handling elf reader #2955
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Passed Diffblue compatibility checks (cbmc commit: bd5d2f6).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/84832352
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am concerned that there will be a long list of different exceptions that are to be caught in the driver programs (and sometimes forgotten to be caught).
Furthermore, there are a lot of similar exception classes, basically containing a string with an error message.
These could be summarised in some base exception class, and then caught by catching the base class.
Can this be resolved by making |
bd5d2f6
to
f17ae97
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Passed Diffblue compatibility checks (cbmc commit: f17ae97).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/85433227
@kroening Would you be able to re-review this PR to see if your blocking comment is still applicable or not? I think it's been addressed now. |
No description provided.