home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sgi:18678 comp.unix.programmer:5887
- Newsgroups: comp.sys.sgi,comp.unix.programmer
- Path: sparky!uunet!stanford.edu!CSD-NewsHost.Stanford.EDU!sparcy.Stanford.EDU!vahe
- From: vahe@sparcy.Stanford.EDU (Vahe Avedissian)
- Subject: developing under sys 5 unix
- Message-ID: <1993Jan11.190843.6808@CSD-NewsHost.Stanford.EDU>
- Originator: vahe@sparcy.Stanford.EDU
- Sender: news@CSD-NewsHost.Stanford.EDU
- Organization: Robotics Lab.
- Date: Mon, 11 Jan 1993 19:08:43 GMT
- Lines: 25
-
- I don't know if anyone else has the same experience,
- but I am always frustrated, and my patience tested
- when developing on SGI or other machines running
- Sys 5 unix.
-
- The real annoying thing is once you run a program
- with a bug, the system tends to completely stop responding
- to interrupts or anything else, the windowing
- system and manager are rendered unresponsive too.
- You just sit there and wait for the system to eventually
- (i.e. anywhere from 3 - 10 minutes or so) core dump.
-
- I've used Sun's for many years and I have rarely seen
- the window manager and entire workstation come to a halt.
- With Sys 5 unix that seems to be the norm rather than
- the exception.
-
- Do I need to reconfigure anything in the kernel/system
- setup or am I stuck (plagued) by this forever ?
-
- Any help or suggestions greatly welcome!
-
- impatient,
-
- vya.
-