Re: 4GL fails w/ segmentation fault

In article <3A54D0E6.610B3A97@informix.com>, Jonathan Leffler <jleffler@informix.com> writes >Denis Melnikov wrote: >> Something strange happens in arbitrary places of 4GL code. Either >> a program fails executing >> OPEN FORM <formname> FROM <filename> >> w/ '-1110 Form file not found' error, or the following >> CLOSE FORM <formname> >> causes program to terminate w/o explanation. >> In both cases 'Segmentation Fault' displayed and core generated. >> The named file does present, of course. Moreover, these commands with >> the same form and file arguments execute correctly in other places of >> the program. >> >> 4GL 7.30UC2 compiled w/ gcc 2.95.1 runs on SPARC Solaris 2.6 > >Over and above what Robert Vorbroker suggested, I'd recommend looking at >the compiler options you are providing -- specifically, you should use >-fwriteable-strings to tell GCC not to trigger core dumps when I4GL >carelessly tries to modify a string literal such as a form name. >Without that option, GCC places the string in read-only memory which >triggers a seg fault when I4GL tries to write to it. > Also 4gl 7.30 had a bug in string handling. Check earlier posts but I think it was something like Let str1 = str2 CLIPPED,str3 CLIPPED resulted in possible memory corruption This bug was fixed in 7.30.UC4. -- David Williams