News for hackers. Stuff that matters.
Re:Fuzzing with american fuzzy lop by slavik81 on Monday October 26, 2015 @01:36PM (#10452911)
The documentation on cppreference is three sentences long, and the invalid inputs get their own line. It's quite clearly documented.

cppreference is a wiki, and that undefined behaviour note was added in 2013 by a user. If you want to help others avoid mistakes by creating documentation, that's a good example of how to do it.

http://en.cppreference.com/w/c/string/byte/isblank

Re:Fuzzing with american fuzzy lop by bhaak on Monday October 26, 2015 @05:05PM (#10454470)
cppreference is documenting the standards and hasn't lots of information about specific implementations.

Technically, this issue is already covered by saying "The behavior is undefined if the value of ch is not representable as unsigned char and is not equal to EOF."

But in reality it is of course hilarious if a simple function like isblank() can crash if though it only check (in the default locale) if its parameter is equal to 9 or 32.

I also checked other libc implementations (IIRC the BSD, OSX, dietlibc and Bionic) and none of the others did crash or even produce surprising results with values outside of the defined range.