Function names again being reported incorrectly in Mythril reports
See original GitHub issueDescription
Looking at the latest master, when verifying fixes made in #469, I find the function names again as being reported as "function": "_function_0xa9059cbb
" in Mythril’s output.
How to Reproduce
myth -xo json 0xfffeee1655f36233fd58fdda74720b4eb85fddec
Environment
- Mythril version: be904f98ccdaec7f90fc6edbffa1d282721eab2e
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
A Practical Guide to Smart Contract Security Tools - Mythril
Let's figure out what went wrong. A solution to this practical issue will help us understand how to run Mythril correctly. The Mythril...
Read more >Mithril Guide application and events - Google Groups
bind() calls execute, leading to new functions always being generated? I'm kind of curious how that works. The first render fires, and a...
Read more >Vetting Smart Contract State-Inconsistency Bugs in Seconds
Abstract—This paper presents SAILFISH, a scalable system for automatically finding state-inconsistency bugs in smart contracts.
Read more >Let's Make PHP's Function Names Consistent! : r/PHP - Reddit
I'm not suggesting PHP is resting on its laurrels, im suggesting you are ignoring the big picture. 1.) Drastic language changes do more...
Read more >Can't execute Mythril on smart contract - Stack Overflow
pip3 uninstall mythril pip3 install mythril ... line 1, in <module> from mythril.analysis.report import Issue File ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
these are versions of modules which
mythril
depends on.upgrading
python3.5
topython3.6
seems to fix this