Try running CB under GDB. Modify a run.sh to execute from the Terminal.
Something like:
# ! / bin / sh <== take blanks out of this line
APP_DIR=/Users/pecan/devel/mac/trunk/src/devel
export LD_LIBRARY_PATH=$APP_DIR:$LD_LIBRARY_PATH
export DYLD_LIBRARY_PATH=$APP_DIR:$LD_LIBRARY_PATH
CODEBLOCKS_DATA_DIR=`pwd`
export CODEBLOCKS_DATA_DIR
gdb $APP_DIR/codeblocks
When you get the crash, type "backtrace full"
and post the results.
You should also be able to start your bundle up like so:
(gdb) run --prefix=/Users/bnilsson
BTW: show me the command line that enables a compile with the debugging option -g.
Is it a configure option?
g++ -g your_source_file.cpp
Strange, I instead find that I need to strip my binaries of debugging symbols afterwards ?
(i.e. that it does build with the -g symbols enabled by default, and is huge because of it)
But they might be talking about the extra Code::Blocks debug code, enabled by configure:
--enable-debug turn on debugging (default is OFF)