I'm looking for troubleshooting suggestions or insights. I'm using Microsoft Visual C++ Version 6. In my MFC application, I can read part of a text file with fgets but, if at some point during that, I open an output file, I then get a "Permission Denied" error (using strerror) on the next fgets and cannot read the rest of the text file. Any ideas?
Have you verified that you even have write privileges in that directory?
carrotcake1029,
Yes, I write to the directory in other programs without a problem. What's even odder, this "Permission Denied" error occurs on the second pass through this piece of code. On the first pass, opening the output file doesn't cause an error, and I can read to the end of the text file. After I posted, I found that if I do _fcloseall() before opening the text file, then I do not get the error. So if that survives rigorous testing, then it's a viable solution. I close the output file if needed before opening a new one, but apparently something there is amiss. I'm just not sure what.
Is fgets() actually failing, or are you just checking errno and seeing that it's non-zero?Originally Posted by Katman
In other words:
Because that would be the wrong way to check for failure -- you'll pick up the error code of whatever happened to fail previously, for instance the attempt to open a file for writing.Code:fgets(...); if( errno ) ...
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
brewbuck,
The fgets fails. Here's the fgets with strerror added in an attempt to identify the error:
If strerror is not returning the fgets error string, what error is it reporting?Code:if (NULL == fgets(linebuf, 99, InputFile)) { sprintf(tmp, "\nstrerror says InputFile read failed: %s\n", strerror( errno) ); MessageBox(NULL, tmp, "Error", 0); } else .....
fgets() might be returning NULL because it is at EOF, not because it experienced an error. Call ferror(InputFile) to see whether there truly was an error on input.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
brewbuck,
Yes, of course I've done ferror already and all that and tested for EOF as well. I think the question has changed somewhat: I open the input file and then close the output file from the first pass before opening a new output file on the second pass. Closing the old output file is a difference between passes 1 and 2. Why does an open input file become "unreadable" after closing an old output file and opening a new output file?
Please consider posting the entire code here, so that we can get a better idea.
