Re: [zeromq-dev] are zmq::atomic_ptr_t<> Helgrind warnings known?

Hi Bill, indeed I've found ThreadSanitizer to be more effective i.e., it contains much less false positives compared to Helgrind... still I'm getting several race condition warnings out of libzmq 4.2.3... indeed I actually built only my application code with -fsanitize=thread... do you know if I

Re: [zeromq-dev] are zmq::atomic_ptr_t<> Helgrind warnings known?

Actually even building zeromq with -fsanitize=thread I still get a lot of data races about ZMQ atomics: WARNING: ThreadSanitizer: data race (pid=25770) Atomic write of size 4 at 0x7d417e48 by thread T4: #0 __tsan_atomic32_fetch_add

Re: [zeromq-dev] zproto- terminated events

[for the search archives] > On Feb 16, 2018, at 9:00 AM, Wes Young wrote: > > (looking at zgossip.c and zgossip_engine.inc, and using versions that are > in-sync with current zproto master) > > in zproto should a “termination” state trigger a socket disconnect (eg: a TCP

Re: [zeromq-dev] are zmq::atomic_ptr_t<> Helgrind warnings known?

I’m using clang’s Thread Sanitizer for a similar purpose, and just happened to notice that the TSAN docs use ZeroMQ as one of the example suppressions: https://github.com/google/sanitizers/wiki/ThreadSanitizerSuppressions

Re: [zeromq-dev] are zmq::atomic_ptr_t<> Helgrind warnings known?

Francesco: Please see my comments below. Full disclaimer: I don’t pretend to understand ZMQ internals, and a lot of this information came via trial and error. YMMV, but I hope this helps. If you find out more, it would be much appreciated if you post back to this thread — thanks! Regards,

Re: [zeromq-dev] are zmq::atomic_ptr_t<> Helgrind warnings known?

There are a couple in the use/setting of a handful of socket options, but nothing major. The pipes and queues are fine. On Sat, 2018-02-24 at 17:34 +0100, Francesco wrote: > Actually even building zeromq with -fsanitize=thread I still get a > lot of > data races about ZMQ atomics: > > WARNING: