On Tue, 2012-08-07 at 17:12 -0700, John Reiser wrote:
On 08/07/2012 04:43 PM, Jacob Goldstein wrote:
--22925:0:schedule VG_(sema_down): read returned -4
That unexpected behavior of sema_down should be investigated.
The code explicitely retry in case read on the sema returns
-4 (i.e.
I created a new Xcode Cocoa project, built and ran it under Valgrind, and the
following leaks are reported. Is this expected? Could this be a bug?
MacOS valgrind --num-callers=200 ./valgrindtest2
==22925== Memcheck, a memory error detector
==22925== Copyright (C) 2002-2011, and GNU GPL'd, by
On 08/07/2012 04:43 PM, Jacob Goldstein wrote:
I created a new Xcode Cocoa project, built and ran it under Valgrind, and the
following leaks are reported. Is this expected? Could this be a bug?
MacOS valgrind --num-callers=200 ./valgrindtest2
==22925== Memcheck, a memory error
