Very Computer

Hi. Since I'm not an expert, I don't know if this is a bug or if it
comes from my system or anything, but I thought it couldn't hurt to
report this, to see if others have the same problem :

I'm running Linux slackware kernel 1.3.73. It's been compiled with
most 'classical' options, with support for the Token Ring driver, the
IBM Tropic chipset, vfat support and the IP_MULTICAST option. My
processor is a 486 DX2/66.
Whenever I do a ps -u (or ps -au or ps -ux or anytime there is the 'u'
option in my 'ps'), I just have the first line (the one with the PID,
GID...) and then the error message 'floating exception'. With every
user, including root.

If you need more details, post here or e-mail me.

                                        Mat

---
One token ring to rule them all, one token ring to find them,
One token ring to bring them all and in the Darkness bind them...

Just a gentle reminder...

Here's a hint:  skim through the subject lines in a newsgroup before you
post a question.  If you're wondering "if others have the same problem,"
then that seems like a wonderful way to find out.  Most likely, someone
has had the same problem, and there's a good chance it has already been
answered.  Skimming before asking saves you time, because the answer may
be before your eyes, and it saves everyone else time, because it reduces
much of the clutter in the newsgroup.

Not to pick on this poster in particular, but I've seen this same question
here at least a hundred times (including followups), and the answer is
always the same:  go to your favorite sunsite mirror site and pick up the
latest procps package (0.99b is current, I think).

--

                  http://marley.hag.housing.washington.edu/jeffgarr

    A hard heart is no infallible protection against a soft head.
                                     - C.S. Lewis, the Abolition of Man

Just today I downloaded the newest version of procps (0.99b ???)
and recompiled.  I had a few problems getting the X utils that come
with the package, but ps works fine now.  Slackware 3.0 comes with
procps as its default, but I think it was at ver 0.98 or so.  The new
one seems to fix what ever problem there is in the new kernel.  No
debugging should not be nescessary.

*snip*

Quote:> Whenever I do a ps -u (or ps -au or ps -ux or anytime there is the 'u'
> option in my 'ps'), I just have the first line (the one with the PID,
> GID...) and then the error message 'floating exception'. With every
> user, including root.

*snip*

Yes.  I have tried 3.72, 74, and 77.  I even checked it after upgrading
the whole OS from Slackware 2.2.0 (a.out) to Slackware 3.0.0 (elf), and
it still occurs.

My solution (which I haven't implemented yet) will be to download the
source, recompile it, and debug it if necessary...

Unless, of course, there is already a fix.  I checked the Slackware
Simplefixes Homepage, but it mentioned nothing about it.

Whaddaya think sirs?

        Known bug since 1.3.5x. Solution is to compile procps.99a.

--
Matt- Linux help by e-mail
Advocating Linux and OS/2 for the Indian Wells Valley

: >*snip*
: >> Whenever I do a ps -u (or ps -au or ps -ux or anytime there is the 'u'
: >> option in my 'ps'), I just have the first line (the one with the PID,
: >> GID...) and then the error message 'floating exception'. With every
: >> user, including root.
: >*snip*
: >

:       Known bug since 1.3.5x. Solution is to compile procps.99a.

Tried this.  Unfortunately, I get make errors when I do this.  I always
get the errors during the 'make' for programs in the xproc directory.  So
I ask a related question:

After upgrading to ELF, do you have to upgrade X Windows to the new ELF
version so that packages like procps compile correctly (this is going to
be my next step)?

--
"My doctor told me to stop having intimate dinners for four, unless there
are three other people."
        --Orson Welles

I've got procps-0.99 today and I tried to compile it with gcc-2.7.0, libc-5.2.18 and
linux 1.3.79. Every time I do a make, I get the following error message during
compilating ps.c:

hendrix-ilha:~/procps-0.99# make
gcc -O4 -I. -Wall -c ps.c
/usr/include/asm/string.h: In function `strtok':
In file included from ps.c:29:
/usr/include/asm/string.h:359: `___strtok' undeclared (first use this function)
/usr/include/asm/string.h:359: (Each undeclared identifier is reported only once
/usr/include/asm/string.h:359: for each function it appears in.)
make: *** [ps.o] Error 1

I've already tried to fix the symlinks for /usr/include/asm, with no success.

Any idea, guys?

HugZ

The problem, also in top and vmstat, and in the 1.3.72 kernel (and maybe
others)is because the code depends on the formatted string in /proc/meminfo.

An extra field was added at the beginning of the second 'line' (try cat
/proc/meminfo to see what I mean) which causes several sscanf calls to
fail, followed by a division by 0.

The solution I adopted was to put two scanf statements where before there were
only one, testing the return code for the number of successful conversions.  In
this way your procps will be backwards compatible with older kernels.

--
John Hickin      Nortel Technology, Montreal, Quebec

: I've got procps-0.99 today and I tried to compile it with gcc-2.7.0, libc-5.2.18 and
: linux 1.3.79. Every time I do a make, I get the following error message during
: compilating ps.c:

: hendrix-ilha:~/procps-0.99# make
: gcc -O4 -I. -Wall -c ps.c
: /usr/include/asm/string.h: In function `strtok':
: In file included from ps.c:29:
: /usr/include/asm/string.h:359: `___strtok' undeclared (first use this function)
: /usr/include/asm/string.h:359: (Each undeclared identifier is reported only once
: /usr/include/asm/string.h:359: for each function it appears in.)
: make: *** [ps.o] Error 1

: I've already tried to fix the symlinks for /usr/include/asm, with no success.

: Any idea, guys?

I got these errors until I got procps-0.99a (can you believe it?).  Make
sure you have the new ELF X libraries or the stuff in procpx-0.99a/xproc
won't compile.

--
If you can lead it to water and force it to drink, it isn't a horse.

Got a Linux problem?  Or can you help others solve them?  Visit the Linux
Common Problems page at http://vortex.cc.missouri.edu/~rhys/linux.html

Justin "Rhys Thuryn" McNutt wrote on 25 Mar 1996 15:39:18 GMT:

Yes, you should.
But meanwhile you can comment out the two subdirs "xproc" and "xcpustate"
in Makefile:

  SUBDIRS    =  skill psmisc # xproc xcpustate # sub-packages to build/install

BTW, that isn't any big loss. xload is included in the XFree package
and the rest ... just forget it. Use xsysinfo or xosview instead.

Uwe

--

Lake of Konstanz                Germany