|
Code snippet below. The SeekToBegin fails because the CFile object has an invalid file handle. But the open returns true, so the code proceeds to die an ugly death. The code is called within a tight loop passing through a couple of hundred files. It feels like I'm overrunning the hard drive or file system, but I have no idea how I might do that... any thoughts are greatly appreciated.
FilePath = (CString)directoryBuf;
FilePath += (CString)"\\uncompressed.unc";
CFileException fe;
if(UncompFile.Open(FilePath, CFile::shareExclusive | CFile::modeCreate | CFile::modeReadWrite), &fe)
{
UncompFile.SeekToBegin();
UncompFile.Write(outBuf, c_stream.total_out);
UncompFile.SeekToBegin();
UncompFile.Write(outBuf, c_stream.total_out);
UncompFile.Close();
cmpCRC = helper.ComputeFileCRC( FilePath );
UncompFile.Remove((LPCTSTR)FilePath);
if(uncCRC != cmpCRC)
{
ErrorString = (CString)infoStruct->sourceFileName + "\n failed CRC test.";
return ErrorString;
}
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
modified 10-Oct-12 13:11pm.
|
|
|
|
|
Okay, I made one change. Just prior to the .Close, I now invoke .Flush().
The main difference between my environment and the old environment is that my laptop is much faster with a solid state disk. Is it possible that there is a race condition inside of CFile? Seems like I'm grasping at straws.
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Why is this code duplicated?
UncompFile.SeekToBegin();
UncompFile.Write(outBuf, c_stream.total_out);
FYI, Remove() is a static method. It will be correct to call it like this:
CFile::Remove((LPCTSTR)FilePath)
The method Remove() can throw an exception
Example here[^]
|
|
|
|
|
Duplicated code: I don't know. I didn't write this code . Not ducking the question, and it did occur to me that if I was creating a file, the initial position would be zero. In testing, I commented out that line only to have the same exception thrown on the write method - bad file handle.
Static Remove and exceptions: noted.
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
FilePath = (CString)directoryBuf;
FilePath += (CString)"\\uncompressed.unc";
What is the purpose of the casts in the above statements?
In the rest of your code you are not checking the contents of fe after the open so you cannot be sure you have a valid handle at that point. It is always advisable to check the return status of every function call dealing with files, rather than assuming they all succeed.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Inherited code, probably done for no particular reason. They're gone now.
Function returns: yup, not going to argue the point.
I'm going to condense this code down to a very tight little application and hammer a hard drive. Adding the flush seemed to stabilize things, but I'm suspicious of memory corruption.
Stay tuned for the next episode of "As the Code turns..." will Charlie find happiness?
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Richard - the fe content only becomes important if the open call fails. Note the weirdness, it's returning true yet with an invalid handle. In the debugger, I can see that the content of the file exception structure is "no error".
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: it's returning true yet with an invalid handle. I find that very hard to believe; I think you are perhaps misreading something.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
if(UncompFile.Open(FilePath, ...)
{
UncompFile.SeekToBegin(); // <--- asserts here. bad file handle...
I don't know how I could misread that. I'm all ears or eyes....
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: I don't know how I could misread that. I suspect there is a lot more going on in that code than meets the eye. You cannot open a file successfully and then immediately find that the handle is bad; it implies a serious bug in the Win32 SDK which would affect just about every system on the planet. The reality is that there is a bug in your code that has, as yet, gone undetected, but without a lot more information we cannot begin to guess where it is.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
I completely agree. Reaching for a bug in Win32 is silly....
and apologies to all for putting this question in the wrong friggin forum.
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Lose all the casting. The cast to CString is implicit; it's not needed and is ugly. The cast from CString to LPCTSTR is in the same boat. As to your problem, I didn't look, I was distracted by all the unsavoury casting.
Steve
|
|
|
|
|
This is just too funny. sigh, in a sad sort of funny....
So, I have managed to muddle along as there simply is no time to re-write this app. Yet. I can get it to run in the debugger under Windows 7, so that's what I've been doing.
Fast forward three months.
New laptop, new Windows 7 install (should be basically the same, but who really knows?), new VM, etc.
Guess what's running now?
Thumps along just fine. I know the bug is still there, I'm not that dellusional.
Charlie Gilley
<italic>You're going to tell me what I want to know, or I'm going to beat you to death in your own house.
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|