Hi!
I've big troulbe in my project.
It's about writing a file via ANSI-C with fopen, fprintf and fclose. It seems to be buggy.
While writing records to a normal ascii file it is all ok. When the programm end normally (with EXIT or at end of MAIN) it is all normal too.
But when the C-Runtime crashes (memory-overflow etc.), the File is always empty, regardless how many records had been written uptil this point. This causes massive trouble 'cause of unreconstructable data.
I build the file with the intrinsinc BUIDL command, then i use only FOPEN, FPRINTF and FCLOSE. I even use FFLUSH, but this takes no effect.
Due to protability issues i don't like to take the intrinsinc-call HPFOPEN, ...
Has anyone any good ideas, why this behavior of the ANSI-C-Lib within MPE/iX (Versions 6.5 and 7.0) is so strange?
Thanks a lot
Regards
Sam
I've big troulbe in my project.
It's about writing a file via ANSI-C with fopen, fprintf and fclose. It seems to be buggy.
While writing records to a normal ascii file it is all ok. When the programm end normally (with EXIT or at end of MAIN) it is all normal too.
But when the C-Runtime crashes (memory-overflow etc.), the File is always empty, regardless how many records had been written uptil this point. This causes massive trouble 'cause of unreconstructable data.
I build the file with the intrinsinc BUIDL command, then i use only FOPEN, FPRINTF and FCLOSE. I even use FFLUSH, but this takes no effect.
Due to protability issues i don't like to take the intrinsinc-call HPFOPEN, ...
Has anyone any good ideas, why this behavior of the ANSI-C-Lib within MPE/iX (Versions 6.5 and 7.0) is so strange?
Thanks a lot
Regards
Sam