User forums > Nightly builds
The 30 December 2018 build (11543) is out.
UberNewb2:
Can't say this is related to CodeBlocks but I was running 11543 at the time, and this is a pretty serious error and problem.
My Windows 10 pc running my project Blue Screened right when I ran my project's executable from within CodeBlocks using Build->Run. It started up and immediately died. Now I can't tell whether my program caused the blue screen, or Code Blocks, or some other process, but I lost a file in the process. It was open in the Code Blocks editor, and after Windows recovered from the blue screen and restarted, the file was empty. I opened it with a hex editor and discovered it was a bunch of zeros. The entire file contents were wiped out. And I probably had several hundred lines of code that were three days old since the last commit.
I am in the process of recovery right now. I am going to attempt to disassemble the .o file and get the source back that way. If that fails, I don't know what else to try. I can't attach any kind of crash report because there wasn't one. I will attempt to find the memory dump created by the crash recovery thing a ma jiggie and see what I can dredge up.
Wish me luck.
oBFusCATed:
--- Quote from: UberNewb2 on January 11, 2019, 05:27:39 am ---Can't say this is related to CodeBlocks but I was running 11543 at the time, and this is a pretty serious error and problem.
--- End quote ---
No, it is not codeblocks.
--- Quote from: UberNewb2 on January 11, 2019, 05:27:39 am ---My Windows 10 pc running my project Blue Screened right when I ran my project's executable from within CodeBlocks using Build->Run.
--- End quote ---
You have hardware or OS/driver problem! User software cannot cause a BSOD on a well working computer! I doubt you're using Windows 98.
--- Quote from: UberNewb2 on January 11, 2019, 05:27:39 am ---..., but I lost a file in the process. It was open in the Code Blocks editor, and after Windows recovered from the blue screen and restarted, the file was empty....
--- End quote ---
For these cases we use backup solutions. In the software development world these are called version control systems. The one which won the battle is called git. Start using it, even for personal projects and you won't have problems like these in the future.
BlueHazzard:
--- Quote ---It was open in the Code Blocks editor, and after Windows recovered from the blue screen and restarted, the file was empty. I opened it with a hex editor and discovered it was a bunch of zeros. The entire file contents were wiped out.
--- End quote ---
Also codeblocks uses some special save procedure to prevent exactly this. It saves the file first in a temporary file, copies the temporary file over the old file and then removes the temp file after the copy process was successful. So there is always a valid file with your content on the system if something bad is happening
Miguel Gimenez:
An useful feature can be warn the user if one of those .temp files is found when loading the project or, if a file fails to load, look for an associated .temp file and restore it.
oBFusCATed:
Doing the save-to-temp-and-move prevents problems only if cb crashes. If the os crashes the file could be in the write caches of the os and it could be lost. In theory the journal should handle such cases, but there is always a chance of total failure.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version