That macro only appears one place, and it's just zeroing some memory. That might make memcheck happy, but probably wouldn't affect helgrind.
On Wed, Jan 15, 2014 at 9:32 AM, Lindley French <[email protected]> wrote: > Not a fork exactly, it's a tool within valgrind to detect race conditions. > The default tool if you don't specify one is memcheck. > > > On Wed, Jan 15, 2014 at 9:24 AM, Charles Remes <[email protected]>wrote: > >> Search your local repository for ZMQ_MAKE_VALGRIND_HAPPY. I assume >> helgrind is a fork of valgrind so it likely has similar issues. >> >> On Jan 15, 2014, at 8:04 AM, Lindley French <[email protected]> wrote: >> >> > I just ran my zmq program through helgrind to track down an unrelated >> error, but I noticed that helgrind *really* has some complaints about >> libzmq. Now, I know helgrind can give plenty of false positives, so maybe >> there's nothing to worry about. I was just wondering, has anyone looked at >> the issues reported by helgrind? Has anyone created a zmq suppression file? >> > _______________________________________________ >> > zeromq-dev mailing list >> > [email protected] >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
