I’m working on an embedded Linux platform and I’ve created an application in C++. The application creates and opens 3 data files using;
1 files declared global
ofstream datafileA;
ofstream datafileB;
ofstream datafileC;

2 files opened in main()
datafileA.open("rawdataA.dat");
datafileB.open("rawdataB.dat");
datafileC.open("rawdataC.dat");

3 write data to the files in add_data()
datafileA <<dataA<<" , "<<"count= "<< count<<endl;
datafileB << dataB<<" , "<<"count= "<< count<<endl;
datafileC << dataC <<" , "<<"count= "<< count<<endl;

4. close files
datafileA.close()
datafileB.close()
datafileC.close()

The application is very simple, it just runs in forever loop writing data to file until the user hits cntrl + c to end the application. Consistantly datafileB and datafileC hold quite a few points, something that looks realistic to the amount of time that the application has been running. DatafileA on the other hand, seems to quit loging after only a small number of datapoints?

Three files all handled identically, data retrieved and written to identically. I can’t seem to figure out why datafileA is consistently not working. Any help is greatly appreciated.

You should show smallest excerpt from your code which is not working, because with this code isn't anything wrong. Stopping an application with CTRL+C is not a good method, if you does not handle this signal (it is SIGINT) in your application and gracefully close all file handles, etc. Can you confirm that data saved in this file is different than for example displayed simultaneously on the screen?

It's funny you ask about printing to the screen as well to verify if the data is still available. I actually did that experiment to test it, in fact the three data points do continue printing to the screen. The B and C files continue to get updated while the A file stops after short value.

I agree that I'm not handling the closing of the application and files very gracefully yet, that could be my problem? I would expect the same problems with all files, not just one.

I'll put together an excerpt and post it, but what I posted was basically a cut and paste of file handling throughout the code.

I'm going to work on the signal( SIGINT) now to see if that works.

Thanks for your help with this.

Have you tried rearranging the order of the writes?
Try another data file, i.e. a fourth see what happens.
Try using C stdio instead.
Are they open for append?

Try open, append, close, open, append, close etc...

So if data on screen and on file are the same then there is no problem with writing file. The bug most probably is elsewhere. Can you show how this data is readed and written?