News for hackers. Stuff that matters.
Re:Out-of-bounds read and write in the glibc's qsort() by jacquesm on Monday February 05, 2024 @04:04PM (#39267155)
That's really the only proper solution for this problem.
Re:Out-of-bounds read and write in the glibc's qsort() by jcranmer on Monday February 05, 2024 @04:46PM (#39267684)
Not necessarily the only proper solution--hard failure, like array out-of-bounds errors, is also often an acceptable solution.
Re:Out-of-bounds read and write in the glibc's qsort() by jacquesm on Tuesday February 06, 2024 @01:54AM (#39271542)
That highly depends on the execution environment. In Erlang for instance that would be an acceptable solution. But most other environments don't deal nearly as gracefully with runtime errors.
Re:Out-of-bounds read and write in the glibc's qsort() by rsaxvc on Tuesday February 06, 2024 @08:38AM (#39274042)
MIPS on GCC defaulted to trapping integer overflows, but they had non trapping instructions too.