Re: 4GL Core Dumps. Help!

Path: emory!att!cbfsb!cbnewsb.cb.att.com!nll From: nll@cbnewsb.cb.att.com (neal.l.leitner) Newsgroups: comp.databases.informix Message-ID: <1991Sep25.115452.9928@cbfsb.att.com> Date: 25 Sep 91 11:54:52 GMT References: <1991Sep25.023838.24446@informix.com> Sender: news@cbfsb.att.com Organization: AT&T Bell Laboratories From article <1991Sep25.023838.24446@informix.com>, by aland@informix.com (Colonel Panic): > 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. > I am not solely attributing the problem to 4GL. I am looking for any reasonable answer. I know that Unix 3.2.3 for the AT&T 6386 allows you to tune parmaters such as ulimit, shared memory, etc. rather easily. To run Informix on the 6386 with 8MB of RAM, are there any tunable paramaters that should be set certain ways to possible allocate enough memory to run the programs without any problems? I also found out from the Informix engineer that using the malloc library to compile programs really hasn't been tested or supported by Tech. Support. Neal Leitner ...att!emdbl1!nll