|
From: Alexander P. <gl...@go...> - 2010-08-09 12:13:34
|
Hi all, I'm getting the following reports while running some Chromium unittests under Memcheck on OS X 10.6: =================================== Syscall param fchmod_extended(xsecurity) points to unaddressable byte(s) __fchmod_extended fchmodx_np copyfile_internal copyfile file_util::CopyFile(FilePath const&, FilePath const&) (/Users/glider/src/chromium/src/base/file_util_mac.mm:30) Syscall param chmod_extended(xsecurity) points to unaddressable byte(s) __chmod_extended chmodx_np copyfile file_util::CopyFile(FilePath const&, FilePath const&) (/Users/glider/src/chromium/src/base/file_util_mac.mm:30) =================================== When I run dtruss on these tests I find out that the syscalls are invoked with almost no arguments: chmod_extended(0x1330000, 0x0, 0x0, 0x0, 0x0) and fchmod_extended(0x5, 0x0, 0x0, 0x0, 0x0) , where 0x5 is a valid file descriptor (it's used by other syscalls) and 0x1330000 is a valid string (ditto). I suspect the reports are caused by some harmless optimization which was not used in 10.5 but appeared in 10.6. Does anyone have any insight about this? Thanks in advance, Alexander Potapenko Software Engineer Google Moscow |