A while back I posted about this horrible, intermittent bug that corrupted all the data in a storage file. After a lot of pain and suffering, one of our testers found a way to reproduce the bug and another programmer on the team fixed it.

The problem was not with Metakit. We had a function that verified read-write access to a storage file before constructing a c4_Storage to open the file. Our verification function called fopen(filename,"w+") and closed without writing to make sure we had access. However, the Windows version of fopen() will write to the file in certain situations. If the last character in the file is 26 (ctrl-z), it will be stripped, causing other problems when Metakit is opened. The bug showed up intermittently, because the last byte was only occasionally set to 26. The programmer fixed this problem by changing the fopen call to fopen(filename "wb+").

So things are good!

-Erik

_______________________________________________
metakit mailing list  -  [EMAIL PROTECTED]
http://www.equi4.com/mailman/listinfo/metakit

Reply via email to