system lockup
Fred Fish
fnf at estinc.UUCP
Fri Feb 17 01:55:50 AEST 1989
In article <555 at marob.MASA.COM> daveh at marob.masa.com (Dave Hammond) writes:
<In article <60 at estinc.UUCP> fnf at estinc.UUCP (Fred Fish) writes:
<<[...]
<<This simple program demonstrates the problem on my system:
<<
<< static char buf [1024 * 1024];
<< main ()
<< {
<< write (0, buf, sizeof (buf));
<< }
<
<I'm not offering confirmation, but I am quite curious why you
<are writing to file descriptor 0, normally associated with your
<standard input -- a *read* descriptor. Perhaps this is contributing
<to your problem?
This is a contrived example which demonstrates the system lockup. The
application was attempting to write to a file that it had opened, but
the file descriptor was getting lost due to a program bug, causing it
to attempt to write to descriptor 0. No, I would not normally attempt
to write 1Mb of null bytes to my standard input stream. However, I
wouldn't expect such an attempt to bring the system to its knees.
-Fred
--
# Fred Fish, 1835 E. Belmont Drive, Tempe, AZ 85284, USA
# 1-602-491-0048 asuvax!{nud,mcdphx}!estinc!fnf
More information about the Comp.unix.xenix
mailing list