Hello
On Wed, 23 May 2001, Jeremy C. Reed wrote:
> On Wed, 23 May 2001, James wrote:
>
> > Does anybody have any idea why a 'top' should do this? It's on a
> > Linux xxxxxx 2.2.17 #1 Mon Dec 18 13:06:46 CET 2000 i686 unknown
>
> What version of procps? (dpkg --status procps)
xxxxxxx:/etc# dpkg --status procps
Package: procps
Status: install ok installed
Priority: required
Section: base
Installed-Size: 315
Maintainer: Craig Small <[EMAIL PROTECTED]>
Version: 1:2.0.6-6
Replaces: bsdutils
Provides: watch
Depends: libc6 (>= 2.1.2), libncurses5
>
> Did you recently change from an older kernel without updating procps?
> (The /proc/meminfo format has changed a couple times.)
The machine hasn't been updated via dselect attall(ever!) and the kernel
definatly hasn't been updated.
I got a scrace.log but I don't understand it :-) The end is here...
fcntl(7, F_SETLKW, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
read(7, "", 384) = 0
fcntl(7, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
rt_sigaction(SIGALRM, {SIG_DFL}, NULL, 8) = 0
alarm(0) = 1
close(7) = 0
open("/proc/loadavg", O_RDONLY) = 7
lseek(7, 0, SEEK_SET) = 0
read(7, "0.00 0.05 0.04 2/44 618\n", 1023) = 24
write(1, "\33[H\33[2J\33[H\33[1m 6:43pm up 43 mi"..., 79) = 79
open("/proc", O_RDONLY|O_NONBLOCK|0x10000) = 8
fstat(8, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
fcntl(8, F_SETFD, FD_CLOEXEC) = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
Thanks for your help.
>
> For example, I have kernel 2.2.14 and procps 2.0.6-5 (Debian package
> version).
>
> Or you can try using gdb to look at any core dump or strace to see what
> top is doing.
>
> Jeremy C. Reed
> ....................................................
> BSD software, documentation, resources, news...
> http://bsd.reedmedia.net/
>
>
