> On 17 Jun 2016, at 14:42, Alex Bligh <a...@alex.org.uk> wrote: > > I am trying to run valgrind 3.11.0 on OS-X 10.11.5 to track down a bug in > Qemu 2.6.0. > > I fully suspect this is: > https://bugs.kde.org/show_bug.cgi?id=354883 > > My question is simply whether I should expect valgrind to work on 10.11 with > threads if I compile trunk from source, or whether I need to look at some > other way of hunting my issue down. > > > .... > > Details:
This appears not to be fixed $ svn info Path: . Working Copy Root Path: /Users/amb/valgrind/valgrind URL: svn://svn.valgrind.org/valgrind/trunk Repository Root: svn://svn.valgrind.org/valgrind Repository UUID: a5019735-40e9-0310-863c-91ae7b9d1cf9 Revision: 15892 Node Kind: directory Schedule: normal Last Changed Author: carll Last Changed Rev: 15892 Last Changed Date: 2016-06-13 18:30:24 +0100 (Mon, 13 Jun 2016) ==80865== Syscall param __pthread_sigmask(set) points to uninitialised byte(s) ==80865== at 0x10588DF36: __pthread_sigmask (in /usr/lib/system/libsystem_kernel.dylib) ==80865== by 0x1059E59B0: pthread_sigmask (in /usr/lib/system/libsystem_pthread.dylib) ==80865== by 0x1003261EE: qemu_thread_create (qemu-thread-posix.c:479) ==80865== by 0x100336302: rcu_init (rcu.c:316) ==80865== by 0x7FFF5FC1310A: ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in /usr/lib/dyld) ==80865== by 0x7FFF5FC13283: ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in /usr/lib/dyld) ==80865== by 0x7FFF5FC0F8BC: ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) (in /usr/lib/dyld) ==80865== by 0x7FFF5FC0F742: ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) (in /usr/lib/dyld) ==80865== by 0x7FFF5FC0F9B2: ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) (in /usr/lib/dyld) ==80865== by 0x7FFF5FC020F0: dyld::initializeMainExecutable() (in /usr/lib/dyld) ==80865== by 0x7FFF5FC05D97: dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) (in /usr/lib/dyld) ==80865== by 0x7FFF5FC01275: dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) (in /usr/lib/dyld) ==80865== Address 0x10540d608 is on thread 1's stack ==80865== in frame #2, created by qemu_thread_create (qemu-thread-posix.c:452) $ valgrind --version valgrind-3.12.0.SVN -- Alex Bligh ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
