home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!crdgw1!rdsunx.crd.ge.com!ariel!davidsen
- From: davidsen@ariel.crd.GE.COM (william E Davidsen)
- Newsgroups: comp.unix.sysv386
- Subject: Re: perl 4.035 induces kernel panic in SVR4
- Message-ID: <1992Sep11.145204.13475@crd.ge.com>
- Date: 11 Sep 92 14:52:04 GMT
- References: <1992Sep7.002515.15426@husc3.harvard.edu> <jrh.715877574@mustang> <1992Sep9.180635.27817@crd.ge.com> <1992Sep10.204557.15522@husc3.harvard.edu>
- Sender: usenet@crd.ge.com (Required for NNTP)
- Reply-To: davidsen@crd.ge.com (bill davidsen)
- Organization: GE Corporate R&D Center, Schenectady NY
- Lines: 19
- Nntp-Posting-Host: ariel.crd.ge.com
-
- In article <1992Sep10.204557.15522@husc3.harvard.edu>, maziere1@husc8.harvard.edu (David Mazieres) writes:
-
- | Thanks for all the help I've gotten. In fact, my problem was simply that I
- | was including libucb before libc. I changed the library flags to -lc -lucb,
- | and the new version tested fine. When I posted I figured I'd probably messed
- | up the flags somehow--the really disturbing thing is that a non-root user can
- | bring the whole system down. I know the ucb library has tons of bugs in it,
- | but should even the most bizarely warped and misused system calls panic the
- | kernel? (i.e. not should as in is this a good thing, but should as in have
- | other people been able to crash their SVR4 kernels reproducibly)
-
- I used to crash Dell regularly with a temp sensitive motherboard ;-)
- Other than that I have never had a panic with Dell (or Intel, when I was
- doing beta on that). It's been totally resistant to software causing
- panics, one of the reasons I like it. I've never corrupted the
- filesystems, either, no that I think of it.
- --
- bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
- I admit that when I was in school I wrote COBOL. But I didn't compile.
-