home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!stanford.edu!rock!sas!mozart.unx.sas.com!jamie
- From: jamie@cdevil.unx.sas.com (James Cooper)
- Subject: Re: Segmentation faults needed
- Originator: jamie@cdevil.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <BrsMBB.HID@unx.sas.com>
- Date: Wed, 22 Jul 1992 13:47:35 GMT
- References: <1992Jul21.190824.7598@emr1.emr.ca> <1992Jul21.222212.29270@cs.rose-hulman.edu>
- Nntp-Posting-Host: cdevil.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 29
-
-
- In article <1992Jul21.222212.29270@cs.rose-hulman.edu>, catapcnl@NeXTwork.Rose-Hulman.Edu (Chris Lawrence) writes:
- >Distribution: World
- >
- >In article <1992Jul21.190824.7598@emr1.emr.ca> dostie@ccrs.emr.ca (M Dostie)
- >writes:
- >:This may be hopeful thinking but is there some utility which will
- >:prevent C programs from crashing the machine and rebooting it and
- >:instead print something like Segmentation fault and return to the
- >:console??
- >:
- >: Mark Dostie
- >: mdostie@ccrs.emr.ca
- >
- >If you use SAS/C, try using the catch.o startup code. This will trap many
- >(though not all) exceptions. As for segmentation faults, that sort of stuff
- >requires protected memory support or a program like MemWatch.
-
- catch.o will catch anything that happens within your program, but it
- won't catch things like sending bad packet info to a DOS or Exec call,
- etc.
-
- --
- ---------------
- Jim Cooper
- (jamie@unx.sas.com) bix: jcooper
-
- Any opinions expressed herein are mine (Mine, all mine! Ha, ha, ha!),
- and not necessarily those of my employer.
-