Re: Coredumps and 4GL

In article <36388F94.5AE@bellsouth.net>, carlson1@bellsouth.net () 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? Its a bit of straw clutching but the I had this problem once and the solution was to split the function in two and stick then in separate modules. The second function was a call that only did a display or something equally trivial. Putting the unaltered into a separate file/module made no difference, adding sleeps and displays only moved the problem around at best and at worst caused it core dump immediately. Paul Watson # I don't suffer from WF Software Ltd. # stress, I'm just Tel. (+44) 1436 674729 # a carrier Fax. (+44) 1436 678693 # www.wfsoftware.co.uk