[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] oprofile callgraph question
From: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] oprofile callgraph question |
Date: |
Mon, 23 Jun 2008 16:13:39 -0700 |
User-agent: |
Mutt/1.5.17 (2007-11-01) |
On Mon, Jun 23, 2008 at 06:53:07PM -0400, Mikyung Han wrote:
> On Mon, Jun 23, 2008 at 6:37 PM, Eric Blossom <address@hidden> wrote:
>
> > On Mon, Jun 23, 2008 at 05:42:16PM -0400, Mikyung Han wrote:
> > > BTW, any suggestion for finding out who caused calling the symbols such
> > as
> > > __ieee754_atan2
> > > and __kernel_cosf, __kernel_sinf, __ieee754_rem_pio2f from libm-2.5.so?
> >
> > What kind of a machine are you running on?
> >
> uname -a gives
> 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64
> GNU/Linux
When inserting the output of opreport in email, can you please keep
your mail tool from wrapping it?
> I guess I need to study the mapping from python code to c files and
> assembly codes. What would you suggest doing, reading, etc in order
> to figure out this mapping and skeleton of ofdm example? My
> eventual goal is to firgure out which piece of code is taking most
> of the resources for ofdm.
Try using grep and your favorite editor, or tags files and your
favorite editor. The python to C++ naming is generally straight-forward:
gr.foo -> gr_foo.cc.
Eric
Re: [Discuss-gnuradio] oprofile callgraph question, Hoo-chang Shin, 2008/06/24