[Bug 1089722] Re: wcslen reads beyond the end of the buffer

[Dave Gilbert]

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
Foundations Bugs, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1089722

Title:
  wcslen reads beyond the end of the buffer

Status in “eglibc” package in Ubuntu:
  Incomplete

Bug description:
  valgrind reports many errors of wcslen reading beyond the end of the
  buffer.  It appears that sysdeps/x86_64/wcslen.S tries do do 64 bit
  reads which can result in reading beyond the end of the buffer if
  there are less than 64 bits left.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1089722/+subscriptions