Friday, August 21 2026 17:56:13
CIP
| Site Name: | bwh002376.bwh.harvard.edu |
| Build Name: | Darwin-13.4.0-x86_64-incr-SL-OFF |
==46650== WARNING: Support on MacOS 10.8/10.9 is experimental and mostly broken. ==46650== WARNING: Expect incorrect results, assertions and crashes. ==46650== WARNING: In particular, Memcheck on 32-bit programs will fail to ==46650== WARNING: detect any errors associated with heap-allocated data. ==46650== ==46651== at 0x23803B705: ??? ==46651== by 0x23803B6B9: ??? ==46651== by 0x23804F3B1: ??? ==46651== by 0x23804EA4F: ??? ==46651== by 0x2380BA89B: ??? ==46651== by 0x2380A86FA: ??? ==46651== by 0x2380A7373: ??? ==46651== by 0x2380A547F: ??? ==46651== by 0x2380B61E7: ??? ==46651== at 0x1D5FC4A: __sigaction (in /usr/lib/system/libsystem_kernel.dylib) ==46651== by 0x10028D88C: kwsysProcessCreate (in /Users/acil-user/Library/Enthought/Canopy_64bit/User/bin/cmake) ==46651== by 0x1101: ??? (in /usr/local/Cellar/valgrind/3.9.0/lib/valgrind/vgpreload_core-amd64-darwin.so) ==46651== by 0x7FFF5FBFD9CB: ??? valgrind: m_signals.c:979 (void handle_SCSS_change(Bool)): Assertion 'ksa_old.sa_flags == skss_old.skss_per_sig[sig].skss_flags' failed. sched status: running_tid=1 Thread 1: status = VgTs_Runnable Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks.
