Re: [Valgrind-users] cachegrind on Darwin

[Luc B. <luc...@ma...>]

On 29 May 2009, at 10:42, Josef Weidendorfer wrote:

> On Friday 29 May 2009, Nicholas Nethercote wrote:
>> On Thu, May 28, 2009 at 6:03 PM, Luc Bourhis  
>> <luc...@ma...> wrote:
>>> Hello there,
>>>
>>> I know it is not implemented yet but I would like to know about  
>>> the roadmap.
>>
>> Actually, it is :)
>
> Ha, I was not sure about this, as I do not have access to an OSX  
> machine.
> Can anybody test whether Callgrind is working, too?

I have just been trying it.

1) first valgrind --tool=cachegrind ls -l
result in
--36548-- WARNING: unhandled syscall: 33554774
--36548--            a.k.a.: 342

That is to say:

/usr/include/sys/syscall.h:#define	SYS_lstat64_extended 342

I read through README_MISSING_SYSCALL_OR_IOCTL and I could probably  
write the necessary patch but I won't have time to even start before  
well into next week. Quite likely one of you will have done it by then!

2) on one of my test program:
	valgrind --auto-run-dsymutil=yes --tool=cachegrind xxxx
followed by
	cg_annotate --auto=yes cachegrind.out.xxxx
and it prints the expected summary information as well as the line-by- 
line information. I haven't looked thoroughly through it to see  
whether it makes sense though.

Luc