Hi everybody,
after spending some time searching the forum and viewing the gprof page, I finally post here, because I can't seem do what I want.
My problem is that I want to profile a plugin for code::blocks. But only the plugin, nothing else. Specially code::blocks itself I don't want to profile. Just my non-contrib plugin.
What I did so far was setting -pg flag to the src target of c::b and to my plugin. This does give me a gmon.out file, but it isn't quit what I want. All c::b's profile information shows up as well (as to be supposed) and it is very difficult to sort out what is from the plugin and what not.
Is there a way that I can only set the -pg flag on the plugin and run c::b , make the plugin do what it should do and get an output file from that, only showing the plugin data?
Regards
frithjofh
Read the docs of gprof and you'll find that it doesn't support shared libraries, sorry, you have to use some other tool.
OK, I must have overlooked that one.
I tried sprof, but it turns out to have a problem with the gclib. It seems it is not being developed anymore either.
How do you developer guys do profiling for your code::blocks plugins? Or is it that you just don't mind?
Regards
frithjofh
You can try to use oprofile, but it was too complex for me.
OK, then I'm not ashamed of having given up on oprofile myself too. On my system I would have had to change the watchdog settings of the kernel to even make oprofile work ... I surrendered. The features sounded impressive though. Maybe some day one of the real developers here (I mean not someone like me) will pick up the glove.