Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Code::Blocks developint hints

(1/3) > >>

rickg22:
If you have tried to debug Code::Blocks, or have any hint related to development, please post it here.

First hint: If you add the following linker options (found experimentally), debugging under GDB shows more info than normally. This is because the linker doesn't rellocate addresses so they're available to the debugger. It's not perfect, but helps alot.

-Wl,--disable-auto-image-base
-Wl,--export-all-symbols
-Wl,--disable-runtime-pseudo-reloc
-Wl,--disable-auto-import

frog-o:
Don't foget to make sure you get rid of all old plugin before recompiling coblocks unless you recompile them to =.  Some times they clash I spet my hour try find thees type of error.

frog-o:
Be very carefule when using  the keyword delete in programs inproper use can cuase your programs to crash.

Don't foget to read the wxwidget manual when programing with wxwidgets.  It sometime tell way to prevent program crash and tell you proper use of the wxwidgets futtion, class, ect..

rickg22:
NEVER, EVER add dependencies without adding the included files to CVS first!

grv575:
JIT debugging

cd C:\mingw\bin
drmingw -i -v
this will install drmingw as the jit debugger (drmingw -u to later uninstall)
(windbg can be installed as the jit debugger with windbg -I but it doesn't support gcc
gcc debug symbols.  it does support vc5/6/7 .pdb files and provides true source level
debugging)

to test:
- create a win32 project using the gcc compiler as default
- place
  __asm("int3");
  somewhere in the code
- compile & run
  gcc -g

- create a win32 project using vc++ toolkit compiler as default
- place
  __asm{ int 3 };
  somewhere in the code
- compile & run
  cl /Zi
  link /debug

links:
windbg - http://www.codeproject.com/debug/windbg_part1.asp
drmingw - http://jrfonseca.dyndns.org/projects/gnu-win32/software/drmingw/

Navigation

[0] Message Index

[#] Next page