My 32-bit PC gave up on me a little while ago and I had to get a new PC. It is a 64-bit PC and I installed 64-bit Ubuntu 12.04 LTS on it.
I receive and install new versions of Codeblocks via the Update function of Ubuntu and the version now is 8599 for 64-bit.
I have noticed some differences from the 32-bit Codeblocks:
1. debug Step-into by keys shift-F7 does not work, but Step-into from Menu or from the Debug both work
2. small things like entering { places the matching } next to it, not under it that I think it did for 32-bit and earlier codeblocks versions. There are other not-so-important things like this.
Sometimes codeblocks crashes on startup. Ubuntu alerts about this and a report is sent to codeblocks, so you may already know about it. Just in case, here is the main error message in the report:
'codeblocks crashed with SIGABORT in std::Rb_tree<wxString.std::pair<wxString const,SquirrelObject>,std::Select1st<std::pair....'
I have only just started using the 64-bit codeblocks for a command-line application and have hit a major problem:
fopen ( logfilename , "w" ) does not work when using the Run command from the Build menu or the Start from the Debug menu. If the logfile does not exist the file is created, but the vfprintf and fprintf do not work. If the file exists logfile is not recreated (timestamp of the original file remains) , the vfprintf still does not add content to the file but fprintf works.
Running the program from the commandline works and also from the Nemiver GUI gdb front-end.
I will continue to work on this. If you can suggest some experiments at the user-level, please let me know.
Ken