Re: Coredumps and 4GL -- followup

> >Carlson@WHSmith wrote: > >> 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? As was already mentioned, "moving" core dumps usually mean you have corrupted something in your memory, like overflowing a string (although I think 4GL truncates rather than overflowing, but don't quote me on that), or an array. I've also seen it happen if you close a window without first exiting from it, something like this: OPEN WINDOW foo INPUT ..... ON KEY F9 CLOSE WINDOW foo CALL somefunction() END INPUT Note that this isn't really legal -- when you return from somefunction(), you should be returned to the window foo, which you just closed. However, as I recall, you didn't actually have to return from somefunction() in order to dump core. June -- june_t@hotmail.com Grounded in Palo Alto, living on Oreo's