News for hackers. Stuff that matters.

A comment on Picking Apart the Crashing iOS String. Parent comment

Re:Picking Apart the Crashing iOS String by throwawayfinal on Thursday February 15, 2018 @03:04PM (#16387091)
displaying language is full of corner cases. imagine having to render both english, japanese, and arabic in the same code paths, and inline with each other

text display code is not so simple as it seems, and don't fall into the trap of "how hard could it really be"

[ Parent | on HN ]
Re:Picking Apart the Crashing iOS String by brian-armstrong on Thursday February 15, 2018 @03:07PM (#16387128)
I'm not saying it isn't hard - I acknowledge that getting it right is a huge task. But the cost of failure should be rendering incorrectly, not crashing or memory corruption.
[ Parent | on HN ]
Re:Picking Apart the Crashing iOS String by jay-anderson on Thursday February 15, 2018 @03:20PM (#16387234)
There was a similar bug about a year ago as well. I'm surprised more fuzzing, static analysis, and general testing hasn't gone into this area since there have been issues found there already. Maybe they have done this extra work and just didn't catch this one. It's hard to know. Still feels like the way it fails is unacceptable.
[ Parent | on HN ]