-
Notifications
You must be signed in to change notification settings - Fork 273
Invalid Java byte-code errors not handled #849
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
Comments
Fix it? |
@jgwilson42: @tautschnig suggests we fix all these errors. Once I've finished my current tasks can we organise it so that I can come off security for a week or so to go through and do this? |
I obviously don't have any management insight, but the comments in both #182 and in here rather read like complaints than action plans. Complaints should be left to users, developers will hopefully produce patches -- do-ocracy. |
That's useful to hear. Hopefully we'll find a route through those who do have management responsibility to get to the point where I can get some time allocated to do some do-ing on these! Some of those people, like you I'm sure, are quite sympathetic to these needs. |
Thanks for the comments, I will look at how we can prioritise your time @NathanJPhillips. |
There are many instances where invalid java byte-code input is not handled. Either it triggers a failed assertion in CBMC (leading to an abort or undefined behaviour if NDEBUG is set - see #182) or else wrong information is silently returned.
An example can be seen at https://github.com/diffblue/cbmc/blob/master/src/java_bytecode/java_types.cpp#L349
The text was updated successfully, but these errors were encountered: