Re: 4GL Core Dumps. Help!

Path: emory!att!rutgers!pyrnj!pyramid!infmx!seashore!randall From: randall@informix.com (Randall Rhea) Newsgroups: comp.databases.informix Message-ID: <randall.685936002@seashore> Date: 27 Sep 91 01:46:42 GMT References: <1991Sep24.045337.22349@informix.com> <1991Sep24.115156.1319@cbfsb.att.com> <1991Sep25.023838.24446@informix.com> Sender: news@informix.com (Usenet News) Organization: Informix Software, Inc. aland@informix.com (Colonel Panic) writes: >Indeed. This is why I fail to understand why you attribute those symptoms >(where once the program failed once, it would continue to fail regularly >until recompiled) to 4GL rather than to the hardware or O/S. Once 4GL has >produced an executable, if the executable itself changes, it's not 4GL's >fault. If you get failures intermittently, depending on data and/or >sequence of events when running the program, that's another story; it may >be 4GL, it may be programmer error, it may be the O/S, or it could even be >hardware. We had a similar problem on a Pyramid a few months ago. After we conviced Pyramid that we weren't writing self-modifying code, they admitted to a bug in their UNIX kernel. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Randall Rhea Informix Software, Inc. Project Manager, MIS Sales/Marketing Systems uunet!pyramid!infmx!randall