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

Painfull debugging

(1/1)

killerbot:
I am trying to debugt yesterday's revision.
Addind a watch is very risky bizznizz : 95% troubles.

Always tons of warning message boxes :
DebuggerTree::BeginUpdateTree() while already in update block.


Help is welcome :-)

Lieven

tiwag:
Did you build the debug-CB using a wxwidgets debug-version ? i tried this in the past (CVS era) and got tons of messageboxes (wxwidgets-warnings) too.

But you can debug CB built with a wxwidgets release-version, just enable debug output.
Then you don't get wxwidgets-warnings and it's working very reliable.

just run the /output/codeblocks to debug the /devel/codeblocks

killerbot:
I am using the wx dll from the therion builds (http://paginas.terra.com.br/informatica/mauricio/codeblocks/).
Dunno if that is a debug build ? Anyone with a link to a release build of wx 2.6.2 ??

Those warning did not show up before, it is very recently. I think.


--- Quote ---just run the /output/codeblocks to debug the /devel/codeblocks
--- End quote ---
I think Rick said you should use the devel/codeblocks for debugging ??

tiwag:

--- Quote from: killerbot on December 11, 2005, 10:20:30 pm ---
--- Quote ---just run the /output/codeblocks to debug the /devel/codeblocks
--- End quote ---
I think Rick said you should use the devel/codeblocks for debugging ??

--- End quote ---

1. the debugger is runnning within the /output/codeblocks
(or copy this working-version to any other location on your harddisk, i.e. x:\programs\codeblocks )
open the codeblocks-project file and build codeblocks (is built to devel\codeblocks)
then set your breakpoints where you want and start debugging

2. the debuggee is the new built devel/codeblocks

3. the debuggee is called from the debugger of course.


the only important thing is, that you must run the debugger from another codeblocks installation
than that you want to debug - that should be clear now

Navigation

[0] Message Index