Comments on: How to avoid error in CEEGTST API ? http://itknowledgeexchange.techtarget.com/itanswers/how-to-avoid-error-in-ceegtst-api/ Sun, 19 May 2013 03:14:28 +0000 hourly 1 By: aceofdelts http://itknowledgeexchange.techtarget.com/itanswers/how-to-avoid-error-in-ceegtst-api/#comment-98272 aceofdelts Wed, 26 Oct 2011 17:59:34 +0000 #comment-98272 Once you got me to focus on memory, it seems that the CGIDEV2 version uses a bigger allocation than the CGIDEV version. Not sure why my predecessors used CGIDEV but switching to CGIDEV2 fixed the problem (maybe it merely moved the problem based on that it seems to do a recalc of the allocation based on other values, but that works for me).
Mike

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/how-to-avoid-error-in-ceegtst-api/#comment-98171 tomliotta Tue, 25 Oct 2011 00:17:58 +0000 #comment-98171 The source code for XXXWRKHTML is available, so you can probably debug just like any other program. Obtain the various source members, compile with debug enabled (if it isn’t already) and dig in.

How big is your output buffer (i.e., your constructed output)? I’d expect it would be limited to under 16MB.

I wouldn’t expect memory leaks to consume the heap since CGIDEV has been so widely used. I’d think more in terms of exceeding a 16MB limit first.

But I see that XXXWRKHTML is using _C_TS_malloc() for its buffer allocations. In that case, the limit should be just under 2GB rather than 16MB. You might investigate including a call to _C_TS_malloc_debug() or _C_TS_malloc_info() before various allocations are done. That should output some info about how much memory is being used.

Tom

]]> By: aceofdelts http://itknowledgeexchange.techtarget.com/itanswers/how-to-avoid-error-in-ceegtst-api/#comment-98162 aceofdelts Mon, 24 Oct 2011 21:17:04 +0000 #comment-98162 Inching closer – I found a call to CEEGTST in the XXXWRKHTML program (procedure ?) in CGIDEV (& CGIDEV2) library. So it’s an IBM program.
Any experience or tips on digging through this ?

]]>