With annotations in place just in the releaseRef like this:
#include valgrind/helgrind.h
// ..
// ..
void releaseRef(){
ANNOTATE_HAPPENS_BEFORE(m_nRefCnt);
int nRefCnt = __sync_add_and_fetch(m_nRefCnt, -1);
if (nRefCnt == 0) {
On Mon, Jan 9, 2012 at 2:45 PM, Joris Koster joris.kos...@aimms.com wrote:
joris@grazer:~/tmp/src$ valgrind --version
valgrind-3.6.1-Debian
In the 3.7.0 release notes you can see that the following bug has been fixed:
243935 Helgrind: incorrect handling of ANNOTATE_HAPPENS_BEFORE()/AFTER()
Ok thanks Bart,
Tomorrow I'll give a go at running/building a 3.7+.
Regards,
Joris
-Original Message-
From: bart.vanass...@gmail.com [mailto:bart.vanass...@gmail.com] On
Behalf Of Bart Van Assche
Sent: Monday, January 09, 2012 5:02 PM
To: Joris Koster
Cc:
On 07.01.2012 22:59, John Reiser wrote:
However, after using callgrind_annotate --auto=yes, there is no information
for a particular function, say, foo. The name of foo in the assembly is
_Z10foo. I checked and evidence show that this function, which is the core
computational part, should
