Re: memory leak (well, kind of...) ?

aland@informix.com (Colonel Panic) writes: >In article <1195@tglobe2.tollpost-globe> ogj@tglobe2.tollpost.no (Oyvind Gjerstad) writes: >>We have a program written in ESQL/C from Informix that is running as >>a daemon. Lately that program has died occasionally. When it dies, it >>writes an message to the terminal that started it: >>> 4GL run-time error number -4518. The 4GL program cannot >>> allocate any more space for temporary string storage. >> >>Have anybody experienced this message from ESQL/C ? What language >>constructs are likely to be the culprit ? >> >Sorry, but this *must* be a 4GL program. A pure ESQL/C program simply >cannot generate a -4518. >-- >Alan Denney aland@informix.com {pyramid|uunet}!infmx!aland > Smith and Wesson: the Ultimate Point-and-Click User Interface. We have tracked down the problem, and it *is* an ESQL/C-program. The problem was that we have functions in our libraries that are used from both 4GL and C. The return from these functions must differ depending on whether they are called from C or 4GL. In this case we had a function that did a retquote() everytime it returned. This apparently filles TSS with return values. This very simple esql/c program demonstrates this: main() { for(;;) retquote("foo"); } -- Oeyvind Gjerstad Systems dept Tollpost-Globe AS N-6301 Aandalsnes/Norway E-mail: ogj@tglobe2.tollpost.no Phone: (+47 72) 26 663 Fax: (+47 72) 26 694