Forum: GNU Radio Profiling GNURadio with gprof

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
0dfa1a815559738fc7e0f17b0cbf9e54?d=identicon&s=25 Thomas Schmid (Guest)
on 2006-05-15 19:07
(Received via mailing list)

I am trying to profile my code with gprof. I configured and compiled
my modules with the --with-gprof option. Next, I run my test script
which uses these modules and the script returns without any errors (I
use a filesource to deliver the data to my modules). Now I should have
the gmon.out file which I can analyze with gprof, but it isn't there.
Any ideas what I am doing wrong? Or can someone give me some hints on
how they profile their GNURadio applications?

Thank you,

745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2006-05-16 00:05
(Received via mailing list)
On Mon, May 15, 2006 at 10:06:14AM -0700, Thomas Schmid wrote:
> Thank you,
> Thomas

Don't use gprof, use oprofile <>.
oprofile takes advantage of h/w performance counters and doesn't
require any changes to your application code.  You can profile fully
optimized code without any (significant) measurement overhead.

The problem with gprof is most likely that since we're running within
python, the initialization code doesn't get called that sets up the
profiling.  In any case, oprofile is a vastly superior solution.
Besides CPU ticks, it's also possible to profile cache misses, etc.
The actual things that you can profile are processor dependent.

This topic is locked and can not be replied to.