[GEM-dev] Re: [PD-dev] oprofile - streamlining Pd/gem patch

B. Bogart ben at ekran.org
Tue May 16 15:25:44 CEST 2006


Hi Johannes,

When I do: autoconf && ./configure && vi Make.config

I only see the following lines containing "[sS][tT][rR][iI][pP]":

STRIP_UNNEEDED ?= --strip-unneeded
STRIP ?= strip

So I'll comment those out and see what happens.

Thanks.
.b.


On Tue, May 16, 2006 2:44 am, IOhannes m zmoelnig said:
> B. Bogart wrote:
>> Hey gem devs,
>>
>> How can I compiled gem without striping it?
>
> when you have already run configure, edit Make.config and replace the
> STRIP-command with "echo"
>
>
>>
>> I'm having trouble trying to use oprofile to profile the gem functions,
>> it
>> seems to just see the internal pd functions.
>>
>> I tried removing the "strip" from the Makefile after doing
>> autoconf/configure but that does not seem to be doing anything.
>>
>> So I'm starting profile with:
>>
>> opcontrol -i /path/to/pd --start
>>
>> Stoping with:
>>
>> opcontrol --shutdown
>>
>> Looking at the results with:
>>
>> opreport -d
>>
>> How can I compile a Gem binary (on linux) so that I can profile with
>> oprofile?
>>
>> Thanks all. I'll think I'll be giving up soon, will be back at it again
>> tommorrow, I really need to figure out what is causing these CPU
>> jumps...
>>
>
> a very simple profiler for linux is qprof.
>
>
> mfgadsr
> IOhannes
>






More information about the GEM-dev mailing list