#81 closed defect (fixed)
valgrind warnings with ld-2.15.so
Reported by: | zooko | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Version: | 0.5.29 | Keywords: | |
Cc: | Launchpad Bug: |
Description
From #44:
Hm, now the warning is back in a subsequent run:
Let's see, here was the rebuild-the-exact-same-version (95c78ce5f08b03be70e5d69e5eb09d7acc1ce420) that I did earlier and it came out valgrind-clean:
https://tahoe-lafs.org/buildbot-pycryptopp/builders/Ruben%20Fedora%20syslib/builds/41
And here is the rebuild of the exact same version again:
https://tahoe-lafs.org/buildbot-pycryptopp/builders/Ruben%20Fedora%20syslib/builds/48
And the same valgrind warnings are back.
David-Sarah told me to use a search engine, and I found this plausible explanation for this warning from Jakub Jellinek:
Change History (2)
comment:1 Changed at 2012-02-17T06:43:41Z by zooko
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed at 2012-02-17T07:18:56Z by davidsarah
Mousing over [6f7d772b70ca2ccd2833056787b254bb9e2a38f7], I get 'No changeset ... in the repository'.
This particular valgrind warning fixed (suppressed) by [6f7d772b70ca2ccd2833056787b254bb9e2a38f7]. There are other valgrind warnings though...