[Bug 1109327]

[Jackie-rosen]

*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.

-- 
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/1109327

Title:
  who command gets "who: memory exhausted" for certain inputs

Status in The GNU C Library:
  Fix Released
Status in “eglibc” package in Ubuntu:
  Fix Released
Status in “eglibc” source package in Lucid:
  In Progress
Status in “eglibc” source package in Precise:
  In Progress
Status in “eglibc” source package in Quantal:
  In Progress
Status in “eglibc” package in Debian:
  Fix Released

Bug description:
  SRU Justification:
  [Impact] 
   * When using who, certain characters can cause issues with eglibc's vfprintf causing memory issues and who to print 'memory exhausted'.

  [Test Case]

   * Download wtmp.clean.
   * locale-gen en_US.UTF-8 # if necessary
   * LANG=en_US.UTF-8 who wtmp.clean
   * If you see 'who: memory exhausted' the test failed.

  [Regression Potential]

   * This patch reverts a change that fixes the issue in BZ #6530.
   * The patch also adds a test case to check for handling of incomplete multi-byte characters.
   * upstream patch URL: http://sourceware.org/git/?p=glibc.git;a=commit;h=715a900c9085907fa749589bf738b192b1a2bda5

  --

  * Description:
  When running who with the attached file we get an error of "who: memory exhausted".
      $ who wtmp.clean

  This works fine in newer versions of eglibc. I was able to determine that coreutils was not the problem
  by using the precise version of coreutils with the raring eglibc version. In that case the problem went away.
  In addition I've compiled the precise version for raring, and the problem is not present.

  * Versions affected:
  This affects current Lucid, Oneiric, Precise and Quantal eglibc versions.
  2.11.1-0ubuntu7.12
  2.13-20ubuntu5.3
  2.15-0ubuntu10.4
  2.15-0ubuntu20.1
  But does not affect Raring eglibc ( 2.17-0ubuntu1 )

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1109327/+subscriptions