Re:Picking Apart the Crashing iOS String
by brian-armstrong on Thursday February 15, 2018 @03:06PM
(#16387109)
I don't know if I agree with that. The sequence here is something like 5 or 6 characters. There's some tens of thousands of unicode characters, which suggests something like (10000)6 combinations to test. Fuzzing might be more fruitful, but even then I'm skeptical it can find obscure crashes. There's no replacement for defensive programming.
[ Parent
| on HN ]
Re:Picking Apart the Crashing iOS String
by jcranmer on Thursday February 15, 2018 @04:46PM
(#16387989)
Concolic execution as a form of whitebox fuzzing is a very effective way to generate these kinds of crashes, especially if the crash is simple enough that it's the input stream that's generating it, and not positioning the program into a very specific state to get this kind of input string to crash it.