User forums > General (but related to Code::Blocks)
Observations for Codeblocks 64-bit version 8599
resander:
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
Jenna:
I use C::b on 64-bit since several years and there are no issues relatred to 64-bit.
--- Quote from: resander on December 09, 2012, 03:18:31 pm ---1. debug Step-into by keys shift-F7 does not work, but Step-into from Menu or from the Debug both work
--- End quote ---
Shift-key is broken on some (?) newer gtk implemetations (or better it can not be recognized by wxWidgets), this is a known issue and stated in the forum several times, but can only be fixed in gtk.
fopen, etc have nothing to do with C::B which is "just" an IDE.
Make sure all paths are correctly set in the projects properties and you have the needed acces-rights.
oBFusCATed:
This is the gtk+ bug report -> https://bugzilla.gnome.org/show_bug.cgi?id=661973
The issue has been fixed and gtk+ should be updated. Talk to your distro maintainers about it.
Alpha:
--- Quote from: resander on December 09, 2012, 03:18:31 pm ---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.
--- End quote ---
--- Quote from: jens on December 03, 2012, 06:19:06 am ---
--- Quote from: Alpha on December 03, 2012, 04:31:34 am ---
--- Quote from: Alpha on November 29, 2012, 11:00:29 pm ---
--- Quote from: ptolomey on November 27, 2012, 07:45:32 pm ---The Code::Blocks repository for Ubuntu linux is ppa: https://launchpad.net/~pasgui/+archive/ppa/
--- End quote ---
I checked into this ppa, and it appears that the most recent build does not contain the SmartIndent* plugins (lost during packaging??).
--- End quote ---
After discussion with pasgui, the plugins apparently do exist, /usr/lib/codeblocks/plugins, but for some reason have the file extension *.do_not_load. You can manually rename them, or re-install Code::Blocks. I found a purge necessary for the re-install to work:
--- Code: ---sudo apt-get purge codeblocks
sudo rm -rf /usr/lib/codeblocks/
sudo apt-get autoremove
sudo apt-get autoclean
sudo apt-get update
sudo apt-get install codeblocks codeblocks-contrib
--- End code ---
--- End quote ---
For other users:
if that happens to you, please try first to run sudo dpkg-reconfigure codeblocks-contrib .
--- End quote ---
Maybe?
resander:
Have done a bit of experimenting and ended up with the following minimal test program:
--- Code: ---extern char ** environ ;
int main ( int argc , char * argv [ ] )
{
printf ( "Press key to continue...\n" ) ;
int val = getchar();
setenv ( "MYVAR" , "123456" , 1 ) ;
int k = 0 ;
while ( environ [ k ] )
{
printf ( "%s\n" , environ[k] ) ;
k++ ;
}
return 0 ;
}
--- End code ---
which prints the 'Press key' prompt, waits for user to input from keyboard and sets and displays environment variable MYVAR.
This does not work (nothing comes out on the screen) when clicking Run on the Build menu. I assume the main is never entered.
It works for Start/Continue on the Debug menu, for Go-to-cursor F4 (placing cursor at the return statement for example) and when running the program from the command line or via GDB from the command line.
Codeblocks comes with xterm as console terminal. I did not notice this at first. The program worked when I changed the console terminal to gnome-terminal.
I remember using xterm and gnome-terminal without problems on the 32-bit PC though...
Ken
Navigation
[0] Message Index
[#] Next page
Go to full version