Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
debugger speed
rickg22:
Good idea :)
Sorry for my over-enthusiastic attitude (see my sig.)
grv575:
--- Quote from: mandrav on January 04, 2006, 07:00:27 pm ---grv575 you can't possibly compare the speed of C::B's debugger with Quincy's... You 're comparing apples with oranges here ;)
--- End quote ---
Well I'm an optimization freak :D
But quincy does do watch variables as well and still has instant reponsiveness. It may have to do with the fact that I'm running a 1.1 ghz centrino as well (tablet - why it's so slow), but the delay is bad enough that you're more inclined to use breakpoints and continue than stepping through 5-10 lines in a function. Is the gdb verbose mode needed then, or what's it used for over the standard output gdb gives?
I remember the only thing quincy does is:
info f(rame)
every line. Not sure exactly what for though - maybe to track which thread it is in or something.
IIRC gprof was a no go on the CB source. Maybe I'll see if there's any good free assembly level call profilers that might be able to zero in on what's taking the most time on this machine.
Der Meister:
--- Quote from: grv575 on January 04, 2006, 11:39:27 pm ---IIRC gprof was a no go on the CB source. Maybe I'll see if there's any good free assembly level call profilers that might be able to zero in on what's taking the most time on this machine.
--- End quote ---
Compuware's DevPartner Profiler Community Edition is a free and imho really good and powerfull profiler. However, it is a plugin for Visual Studio and I don't know if it is possible to get Code::Blocks compiled with MS Visual Studio and this profiler. But maybe I'll give it a try if I find some free time.
rickg22:
grv: Is Quincy opensource? We might... *ahem* re-use *ahem* some of its code :lol:
mandrav:
--- Quote from: grv575 on January 04, 2006, 11:39:27 pm ---IIRC gprof was a no go on the CB source. Maybe I'll see if there's any good free assembly level call profilers that might be able to zero in on what's taking the most time on this machine.
--- End quote ---
You have to enable profiling only for one target at a time, not globally in project. This happens because, unfortunately, you can't specify an output file when using -pg...
So, just enable profiling on the debugger plugin only and you got yourself some profiling info ;)
Note though, that I 'm not finished with the debugger plugin. It has some optimization opportunities but it's still early for it...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version