Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: frithjofh on October 07, 2009, 11:43:09 am
-
Hello everybody,
I don't know how to attack this problem: a c::b plugin is a shared library, right? So how can I profile just that plugin? Do I have to set up a small test project serving as environment for the plugin, or how do I do it?
Many thanks for any help, regards
nausea
-
I think, oprofile on linux could do it, but it needs lots of reading and trying.
When I tried, I've failed to output something that can help me.
gprof, is not meant to profile apps and sharedlibs togather, unfortunately... :(
-
So it seems as if I would have to set up a minimal app, putting the code of the plugin into it, and fake (so to say) the plugins execution that way ...
Is this how you developers do it ( :? I'm not including myself as developer, I'm just a beginner :? ), when you profile a library, or how ... ???
Greetings from Asturias
nausea