[tahoe-lafs-trac-stream] [pycryptopp] #44: test what happens if another Python module loads Crypto++ dynamic link library

[pycryptopp]

#44: test what happens if another Python module loads Crypto++ dynamic link
library
-------------------+--------------------------
Reporter:  zooko   |          Owner:  zooko
    Type:  defect  |         Status:  assigned
Priority:  major   |      Milestone:  0.6.0
 Version:  0.5.19  |     Resolution:
Keywords:          |  Launchpad Bug:
-------------------+--------------------------

Comment (by zooko):

 The valgrind warnings have gone away. None of the patches we committed
 between when it was giving warnings and when it wasn't would seem to
 explain it. I found a build that had the warnings and that didn't involve
 any experimental patches not destined for trunk, and hit the "rebuild"
 button on that. Buildbot rebuilt the exact same source, based on the git
 hash. This time there were no valgrind warnings! Hooray for the rebuild
 button! Comparing the outputs from show-tool-versions for the builds with
 and without valgrind warnings:

 {{{
  buildmaster: buildmaster: no such file or directory
  buildslave: Buildslave version: 0.8.5 Twisted version: 11.1.0
  cl: cl: no such file or directory
 -g++: g++ (GCC) 4.7.0 20120119 (Red Hat 4.7.0-0.8)
 +g++: g++ (GCC) 4.7.0 20120126 (Red Hat 4.7.0-0.10)
  cryptest: 5.6.1
  darcs: 2.7.98.3 (beta 3)
  7za: 7za: no such file or directory
  flappclient: Foolscap version: 0.6.3 Twisted version: 11.1.0
 -valgrind: valgrind-3.6.1
 +valgrind: valgrind-3.7.0
  as: GNU assembler version 2.22 Copyright 2011 Free Software Foundation,
 Inc. This program is free software; you may redistribute it under the
 terms of the GNU General Public License version 3 or later. This program
 has absolutely no warranty. This assembler was configured for a target of
 `x86_64-redhat-linux'.
  setuptools: [distribute 0.6.24 (/usr/lib/python2.7/site-packages)]

 }}}

 Either Fedora updating to a newer version of the (not yet released)
 gcc-4.7.0 or Fedora upgrading valgrind from 3.6.1 to 3.7.0 could explain
 the warnings going away. In either case, we can consider them to be not a
 problem.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/pycryptopp/ticket/44#comment:18>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>