Peter Martin(deleted)
|
Re: AW: profiling usage of libc
|
Peter Martin(deleted)
08/19/2009 11:21 AM
post36284
|
Re: AW: profiling usage of libc
On Wed, 19 Aug 2009, Hans-Peter Reichert wrote:
>Date: Wed, 19 Aug 2009 11:14:16 -0400 (EDT)
>From: Hans-Peter Reichert <community-noreply@qnx.com>
>Reply-To: post36279@community.qnx.com
>To: general-ide <post36279@community.qnx.com>
>Subject: AW: profiling usage of libc
>
> :-/ I should add the answers I don't like to hear to my posts
>
Isn't it just avoiding passing those compile options to the lib/c/prof
section of the code?
Peter
>
>> -----Ursprüngliche Nachricht-----
>> Von: Colin Burgess [mailto:community-noreply@qnx.com]
>> Gesendet: Mittwoch, 19. August 2009 17:04
>> An: general-ide
>> Betreff: Re: profiling usage of libc
>>
>> You could compile libc with -finstrument-functions, but you might have to be
>> careful that any functions that libprofiling uses don't cause a recursive
>> loop-o-death!
>>
>> Hans-Peter Reichert wrote:
>>> I want to analize libc usage of a certain binary, but I can't find an
>>> instrumented libc.so. so is there any other way than writing a LD_PRELOAD
>>> libc wrapper to get the -finstrument-functions in libc?
>>>
>>> TIA
>>> hp
|
|
|