Hello friends I use nightly5911;mingw345 and gdb 7.0.2. When I try to debug it is possible that I have to wait about 5 to 8 minutes for disassembling before my breakpoint is active.
Have anybody also this strange behavior???
Have you read this thread? I saw no match; but, I do not use debug very much.
http://forums.next.codeblocks.org/index.php/topic,11301.45.html
Tim S.
Please enable the debugger's debug log :)
There you can see what commands are executed.
Find the disassembly command and execute it manually, to see if it is fast, if not it is a gdb problem.
Also you could try a newer gcc (not sure if it is related).
Quote from: oBFusCATed on November 26, 2009, 09:38:47 AM
Also you could try a newer gcc (not sure if it is related).
As far as I know, 7.02 is the newest available gdb on windows. :oops: sorry misread your post, but gcc3.4.5 might have problems with gdb 7.0.2, you coud try TDragons's gcc 4.4 to see if the error disappears : http://tdragon.net/recentgcc/ (http://tdragon.net/recentgcc/), or use an older gdb (6.8.50).
I use also QT453 and as far as I know mingw345 is at the moment standard.
Ok now I install this one :tdm-mingw-1.908.0-4.4.1-2.exe with gdb 7.0.2 I have the same problem
I am waiting toooo long for disassembling codeblocks takes 114 mb by 50 percent cpu and gdb takes ca. 400 mb by 0 % cpu?????
and know is it a CB(5911) or gdb problem
What about the debuggers log : settings -> compiler & debugger -> debugger -> enable debuggers log (debug) (I don't remember the wording of the option name, though) ?
If you could provide a minimal project that can help
Hmm the projct is too big. I set the breakpoint in a function which is very massive.
is there a possibility to deactivate diassembling? Do I really need the disassembling during debugging??
Close the disassemble window and the command for disassembling won't be called.
thanx :lol: