User forums > General (but related to Code::Blocks)

Profiler/Debugger for mingw?

(1/3) > >>

darklordsatan:
I think the title says it all...
For many years, Ive overcome the need to use a profiler and a debugger, now Im thinking on using some...

Do you guys know of a good profiler (and free), and from what I know, a profiler can either be used stand-alone or inside an IDE, so I hear for suggestions... in any case, it must work for mingw (and terrific it could be used inside c::b but I guess this would require a plugin)

And a good debugger (with GUI)? I know you can use gbd with code::blocks, but isnt it like a console app or something? I want some graphical interface (Ive heard there is Insight, but dont think it works with c::b, does it?). In any case it should be free, and work with gcc/mingw, and plus if it can work inside c::b

Any thoughts, suggestions? Am I dreaming (yeah, its 2:00 am so probably I am)

mandrav:

--- Quote ---Do you guys know of a good profiler (and free), and from what I know, a profiler can either be used stand-alone or inside an IDE, so I hear for suggestions... in any case, it must work for mingw (and terrific it could be used inside c::b but I guess this would require a plugin)
--- End quote ---

gprof.
It's included with mingw. A gprof plugin for C::B is already requested but you can still use it without it.
1) In your project build options, check "Profile code when executed"
2) Re-compile your project
3) Run your project and work with it for a while
4) When you exit your project, a file called gmon.out will be created in the same dir
5) Open a command-line in that dir and run "gprof {your.exe} gmon.out > gprof.txt"
6) Open gprof.txt with a text editor like notepad and look what your bottlenecks are :)
7) Rinse and repeat until all bottlenecks have been identified and removed ;)


--- Quote ---And a good debugger (with GUI)? I know you can use gbd with code::blocks, but isnt it like a console app or something? I want some graphical interface (Ive heard there is Insight, but dont think it works with c::b, does it?). In any case it should be free, and work with gcc/mingw, and plus if it can work inside c::b
--- End quote ---

I don't get it. Yes, gdb is a command-line app but C::B hides this fact and you operate gdb with the help of C::B (graphical).
Either you have to restate your question or you 're missing something essential about debuggers and debugging...

Yiannis.

darklordsatan:
Ok, about the profiler, thats nice, thanks...

On the debugger, bare with me, this is new ground, now I get it: it hides the fact its a command line app by providing a menu and stuff (breakpoints), ok... Probably Im just used to the fact people asked around the devcpp forums for insight or something like that, but it would only crash devcpp and thats why you should stick to gdb only in devcpp...

mandrav:
Not to be misunderstood about the debugger:
I 'm not stating that C::B exploits the debugger's capabilites to any extent (maybe 0.00001%). It just allows you to use the most usual commands (like setting breakpoints, stepping, continuing, watching vars, disassembly, backtrace, etc) of gdb.
Consider it an on-going work in progress ;)

Yiannis.

darklordsatan:
Ok.
About the gprof plugin, is anyone working on it? what should it do for a start? maybe making what you mentioned in the command line by means of a dialog or something?

Navigation

[0] Message Index

[#] Next page