Have you got any examples?
IMHO this can just be a false positive since it's safe to read beyond a buffer
end iff:
* You know you're not crossing a 64bit boundary (since you know you're not
crossing a page boundary and hence can't seg)
* Don't cause any data in that 64bit read to influence the result if it's
after the terminating character.
If you've got an example that shows where it breaks either of those two
conditions then I agree it's eglibc bug, else I say it's a false
positive from valgrind.
** Changed in: eglibc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089722
Title:
wcslen reads beyond the end of the buffer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1089722/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
