Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Timeout and max-depth results
See original GitHub issueIn the current version, hitting either the max-timeout or max-depth limit results in Mythril returning an innocent looking output like this -
{"error": null, "issues": [], "success": true}
Can we please have a separate indicator in the output to suggest that the lack of an issue was because of hitting this limit. Currently, there’s no real way to distinguish between Mythril genuinely not finding a bug vs. Mythril returning “no error” simply because it hit one of these limits.
This, in my opinion, is quite a critical flag to have in the output. I’m not sure, but i thought i had raised this issue a while back. Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Priority isn’t yet added, enhancement is just a category in categories like feature, bug, maintainence, … .
This should be resolved with the many changes leading up to 0.20.0. I’m going to close this issue. Feel free to re-open if there are still unresolved problems