Re: es sucking up processor time...

[Paul Haahr <haahr@netcom.com>]

Soren Dayton wrote
> I am finding that an idle es process is taking up quite a bit of
> processor time to do nothing.  About 80% of one of two processors on
> this Sparc 20 actually.

And then...
> 	Jim Davis recommended that I provide a trace of this.
> 
> woodlawn% ls -al trace-es
> -rw-r--r--  1 csdayton  4702295 Sep 18 19:45 trace-es
> 
> woodlawn% uniq trace-es
> ioctl (0, 0x40125401, 0xefffe158) = -1 ENXIO (No such device or address)
> 
> I let it sit for a couple of minutes

I haven't seen this happen.  Does it happen when running under a
debugger?  Can you attach to it and find the troublesome call?

The ioctl request number seems surprising (bogus) for a Sun.  It also
doesn't look like a reasonable permutation of the one ioctl which es
issues directly.  I think it's probably buried in the readline code.

What OS and compiler are you running?  Are you sure your header files
match your compiler?  Similar problems have happened if readline is
compiled with an ANSI C preprocessor, but you're using an old set of
header files -- notably, the SunOS 4 headers.

Paul