Skip to contentSkip to conversation

2.5.40 (BK of today) vmstat SIGSEGV after reading /proc/stat

DISCUSSION Patrick Mau 2 participants 2 messages Oct 5, 2002

lore
Share & tools
lore
#0 lore raw

Hallo List,

The BK tree of today changed the data returned in /proc/stat. A 'vmstat -n 10' immediatly segfaults after reading ...

open("/proc/stat", O_RDONLY) = 6
read(6, "cpu 404408 506514 8240 154301 1"..., 4095) = 714
close(6) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

I'll try to prove a diff between 2.4.18 and BK current later this evening ...

cheers,
Patrick

#1 lore raw

killed by SIGSEGV +++

Quoted 8 lines · Patrick Mau

The BK tree of today changed the data returned in /proc/stat. A 'vmstat -n 10' immediatly segfaults after reading ...

open("/proc/stat", O_RDONLY) = 6
read(6, "cpu 404408 506514 8240 154301 1"..., 4095) = 714
close(6) = 0

killed by SIGSEGV +++ renamed from SIGSEGV (Segmentation fault) --- +0 -0

The format changed, on purpose. You need vmstat from a newer version of procps. The newest version (2.0.9) and CVS dumps as-of yesterday are available at:

	http://tech9.net/rml/procps

as both tarballs and RPM packages.

Robert Love