Re: Coredumps and 4GL -- followup

David Williams wrote: > > In article <3638DA56.3503@bellsouth.net>, Carlson@WHSmith > <carlson1@bellsouth.net> writes > >Carlson@WHSmith wrote: > >> > >> 4GL: 7.20.UD2 > >> Engine: 7.23.UC11 > >> OS: HPUX 10.20 > >> > >> I've just about had it -- hopefully someone out there can pull me back > >> from the brink. 8-) > >> > >> I have a 4gl program that has been running since the 4.1 days. It > >> declares a cursor for an outer loop, then it processes each row. It > >> survived the conversion to 6.0x; now we're running 7.20.UD2. For some > >> reason now it core dumps on me. > >> > >> When I add a few displays (yeah, we're IFMX-debugger-deprived), I'm able > >> to see where it is in the program when it dumps. When I add a few other > >> displays, the location changes. > >> > >> When I clean up the code ( close cursor / free cursor ), it runs a bit > >> longer and then still coredumps. > >> > >> I remember the 'old' (4.1) days where a display or a sleep would "take > >> care" of the problem, but this is ridiculous. Anyone out there have any > >> ideas? > >> > > > >Followup: > > > >compiled c4gl with -otherargs -g in order to check with xdb; code ran > >with no problems. Eliminated all display statements, still ran. > >Eliminated close / free cursor statements; program coredumped. > > > >Made corrections to original program and added close / free cursor; > >program ran. > > > >I opened a call with Informix anyway, just to check. > > > >Such are the ways of 4gl, I guess. > > > > > > Compile with > > c4gl -a -anyerr > > -a = array bounds checking > > bet you are running off the end of an array.. No arrays in the program, but I checked that Friday last week...came up clean . . . . (sigh!) John Carlson Informix DBA WHSmith, Inc.