Making sense of ktrace(1) output

[Garrett Cooper]

Roman Divacky wrote:
> On Mon, Jun 18, 2007 at 01:55:01AM -0700, Garrett Cooper wrote:
>   
>> Peter Jeremy wrote:
>>     
>>> On 2007-Jun-18 00:39:44 -0700, Garrett Cooper <youshi10 at u.washington.edu> 
>>> wrote:
>>>  
>>>       
>>>> However, I was able to get ktrace output. The only problem is that 
>>>> ktrace(1) apparently outputs only in binary, instead of plaintext output. 
>>>> Can I convert it to plaintext somehow and process it?
>>>>    
>>>>         
>>> kdump(1)
>>>
>>>  
>>>       
>> grazi to all that replied -- that did the trick :).
>>
>> Now, note to self.. never ever do analysis on something so large as 
>> pkg_add thunderbird. Really, really bad idea :)..
>>
>> I'll make up some Perl scripts, produce some histograms, and see if I 
>> can better trace down this bottleneck.
>>     
>
> well.. instead of using ktrace I'd suggest building profiled pkg_add
> and see that way where the time is spent. ktrace is great if you dont
> have the source code... but you do :)
>
> roman
>   
    Unfortunately I have to profile all of the source up the tree to 
create profiled symbols, and I'm running into some issues profiling 
liblegacy.
    Does anyone have any hints for getting around that, or just 
profiling all of the relevant libs?
Thanks,
-Garrett