home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!ucbvax!VNET.IBM.COM!metaylor
- From: metaylor@VNET.IBM.COM (Mark E Taylor)
- Newsgroups: comp.unix.aix
- Subject: Re: Follow-up: Re: Debuging Segmentation Violation Fault
- Message-ID: <9208180827.AA18954@ucbvax.Berkeley.EDU>
- Date: 18 Aug 92 08:58:48 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Reply-To: metaylor@vnet.ibm.com
- Organization: IBM UK Laboratories
- Lines: 18
-
- Jing Huang writes:
- > However, to my great surprise, it later turned out that nothing was
- >wrong with my program. It was the system's library which got corrupted. And
- >I did not find this out until someone else took my favorite seat and I was
- >forced to use another computer (we have 9 AIX). I would have never suspected
- >the system itself and could have spent my whole life (?) in vain.
-
- If you get a crash on one machine but not on another, it's very
- probable that there's a bug in your program. The behaviour of the
- S/6000 hardware has changed. Early machines will let you dereference NULL
- but more recent machines will coredump. Add to that the stricter
- behaviour of malloc under AIX 3.2, and it's still likely that you're
- seeing delayed effects of your program writing beyond a malloced area.
-
- Mark E Taylor
- AIX Solution Engineering Services
- IBM UK Laboratories, Hursley, England
-
-