Re: [Valgrind-developers] valgrind: r8927 - in branches/DARWIN: coregrind include

[Greg P. <gp...@ap...>]

On Jan 8, 2009, at 3:55 PM, Nicholas Nethercote wrote:
> On Fri, Jan 9, 2009 at 10:52 AM,  <sv...@va...> wrote:
>> Author: njn
>> Date: 2009-01-08 23:52:26 +0000 (Thu, 08 Jan 2009)
>> New Revision: 8927
>>
>> Log:
>> DARWIN/coregrind/m_debugstub.c
>>   Adhere to "Valgrind style":
>>   - Use VKI_ constants rather than the originals
>>   - Use VG_(memcpy) rather than memcpy()
>
> Greg, any idea why 'memcpy(...)' worked?  I thought it wouldn't,
> because libc isn't linked with Valgrind.  Or is it on Darwin?  Or is
> GCC using a builtin memcpy?

No, we don't use libc either. My guess is a builtin. Try compiling  
with -fno-builtin to catch any others.

(We do have a captive copy of the dynamic linker and dyld itself  
includes some parts of libc. But there's nothing there that would make  
memcpy work.)


-- 
Greg Parker     gp...@ap...     Runtime Wrangler