[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:  closed
Priority:  major   |      Milestone:  0.6.0
 Version:  0.5.19  |     Resolution:  fixed
Keywords:          |  Launchpad Bug:
-------------------+------------------------
Changes (by zooko):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 Okay, so the whole thing about the valgrind warnings starting in
 comment:12 was a red herring -- those warnings were almost certainly
 unrelated to the subject of this ticket.

 I also just opened #82 to be about the last remaining valgrind warnings,
 which appear to be unrelated to this issue.

 As for the actual subject bug(s) of this ticket, I think they can be
 marked as "presumed dead":

 * Raising exceptions from one shared library ({{{libcryptopp.so}}}) and
 catching it in another ({{{_pycryptopp.so}}}) is tested and works (see
 comment:5
 * Setting {{{RTLD_GLOBAL}}} cured the double-free errors on all platforms
 where they occurred, setting it back to {{{RTLD_LOCAL}}} later re-
 introduced them and setting it back to {{{RTLD_GLOBAL}}} again cured them
 again
 * I applied Wei Dai's patch in [95c78ce5f08b03be70e5d69e5eb09d7acc1ce420]
 and while it didn't cause anything to improve on the buildbot, it didn't
 cause anything to degrade either (and I inspected the patch and didn't see
 any bugs in it)
 * Valgrind isn't telling us about any potential problems that are related
 to this ticket
 * We changed it so the double-load-tester is actually loading the Crypto++
 dynamic-link library necessarily (by making it use a symbol provided by
 that library, per comment:8), in
 [7b821f79032fcba0e956813d1be93d19eef7d103]

 So, I'm going to mark this ticket as "fixed".

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