Hacker News new | ask | show | jobs
by wyldfire 3587 days ago
> Damn. That's terrible. We are never going to get anywhere with 20 executions a second

...

> Lucky for us there is a trick we can use to greatly improve that speed.

I just dusted off my fuzzpy project [1] this week and was bringing it up to date with recent CPython, LLVM/libFuzzer.

> Notice the speed: 373.4/sec, up from 20! And we've already found 100 unique crashes!

Most of my test cases run at < 10/sec. I feel like I just got lapped while I thought I was on a casual solo stroll. O.o

I intentionally left Py_InitializeEx() in the critical section for fear of contaminating global state, though. But I see that I should've at least experimented with it out.

[1] https://bitbucket.org/ebadf/fuzzpy

EDIT: sorry, I went a little off the deep end -- this post is in response to the article listed in the first paragraph "After finding 1800+ crashes in Python 3.5 using a method shown here ... "

2 comments

I didn't get the point of the 1800+ crashes. Python isn't designed to be safe from corrupted byte code in the .pyc files.
Yolo! :P