🚀 go-pugleaf

"Ronald Boucher" <ron.boucher@xerox.com> wrote:
>
>I have created a function which pull the data info from a chip and save & append to a single file, then returns a int value which indicate success/failure.
>
>When I click the button to call the read/dump function about 45 times, the file somehow cannot be opened.  I checked out the memory address of file object "fp" (from FILE* fp declaration).  After 45 times, the fp address turned out to be null... I wonder if that means the fp address has ran out of place to open an new address?  I had to restart the application to continue with the rest of the chips after 45 calls.  How do I reset the memory address or keep it the same?  The file name is generated,
>depending on validity of the chip, line number, date, and the program name.  Anyone help? 
>
>Sample Code: 
>(note: output variable is char[] array for chip info.)
>
>
>#include <fstream.h>
>
>int Dump::DumpCRUM(char mode) 
>// mode variable is used for either 'f'ilter or 'm'ain modules
>{
>  // FileName string is generated
>  
>  ofstream dumpfile(FileName.c_str(), ios::app);
>  if (!dumpfile)
>    {
>      return -1;
>    }
>  else
>    {
>      dumpfile << output;
>      dumpfile.close();
>    }
>  return 1;
>}
>
>I haven't created a constructor & destructor in this Dump class.  Perhaps this will help?
>

This code was written on the dump.cpp file. I have investigated from our original source code and spotted one thing I missed. I realized that when creating the filename string, it caused the stream buffer to overflow. So I had to add one line code (just after "dumpfile.close();") with "FileName = NULL;". This will help to free up the file stream buffer, and to prevent overflow.