[Bug 1242746] Re: SIGSEGV when file2str reads zero bytes

[John-Mark Bell]

Dave: I've been seeing this about twice a day since I picked up the new
packages (about a week ago).

I've got a cron job that runs every 5 minutes, and one of the things it
runs is "top -c -b -n 2 -d 2", which is what's exploding for me.

The systems this job runs on tend to be transient (they're autodeployed
systems in my regression test network), so would rarely exist for a
prolonged period of time.

So, to answer your question: it clearly doesn't happen every time, but
happens sufficiently often to cause me pain!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1242746

Title:
  SIGSEGV when file2str reads zero bytes

Status in “procps” package in Ubuntu:
  New

Bug description:
  The changes made in the following commit, which backported a number of
  changes to the procps package in precise, result in various procps
  utilities crashing with a SIGSEGV if the file2str function in
  proc/readproc.c reads zero bytes.

  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/procps
  /precise-updates/revision/61

  This corresponds to the following procps package version:
  1:3.2.8-11ubuntu6.1

  Prior to this changeset, file2str would return -1 if the read failed;
  now it does not, which is not expected by other parts of the procps
  codebase, hence the crash.

  Upstream have fixed this issue in the following commit:

  https://www.gitorious.org/procps/procps/commit/526bc5dfa924177e68be0123bd67e3370955f924

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