[tahoe-dev] [pycryptopp] #24: SHA256 failure on NetBSD with multiple segments
pycryptopp
trac at allmydata.org
Wed Jul 1 00:56:17 PDT 2009
#24: SHA256 failure on NetBSD with multiple segments
----------------------+-----------------------------------------------------
Reporter: warner | Owner: bdew
Type: defect | Status: new
Priority: critical | Version: 0.5.1
Keywords: integrity | Launchpad_bug:
----------------------+-----------------------------------------------------
Comment(by bdew):
Aha! Now i built it without SSE2 support (adding CRYPTOPP_DISABLE_SSE2)
and the test passes (and valgrind too):
{{{
==26122== Memcheck, a memory error detector.
==26122== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
==26122== Using LibVEX rev 1884, a library for dynamic binary translation.
==26122== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP.
==26122== Using valgrind-3.4.1-Debian, a dynamic binary instrumentation
framework.
==26122== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al.
==26122== For more details, rerun with: -v
==26122==
running darcsver
running test
running egg_info
writing requirements to pycryptopp.egg-info/requires.txt
writing pycryptopp.egg-info/PKG-INFO
writing top-level names to pycryptopp.egg-info/top_level.txt
writing dependency_links to pycryptopp.egg-info/dependency_links.txt
writing manifest file 'pycryptopp.egg-info/SOURCES.txt'
running build_ext
copying build/lib.linux-i686-2.5/pycryptopp/_pycryptopp.so -> pycryptopp
test_chunksize (pycryptopp.test.test_sha256.SHA256) ... ok
----------------------------------------------------------------------
Ran 1 test in 10.929s
OK
==26122==
==26122== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3736 from
9)
==26122== malloc/free: in use at exit: 4,983,817 bytes in 906 blocks.
==26122== malloc/free: 325,282 allocs, 324,376 frees, 71,999,912 bytes
allocated.
==26122== For counts of detected errors, rerun with: -v
==26122== searching for pointers to 906 not-freed blocks.
==26122== checked 5,115,828 bytes.
==26122==
==26122== LEAK SUMMARY:
==26122== definitely lost: 0 bytes in 0 blocks.
==26122== possibly lost: 66,612 bytes in 181 blocks.
==26122== still reachable: 4,917,205 bytes in 725 blocks.
==26122== suppressed: 0 bytes in 0 blocks.
==26122== Rerun with --leak-check=full to see details of leaked memory.
}}}
--
Ticket URL: <http://allmydata.org/trac/pycryptopp/ticket/24#comment:7>
pycryptopp <http://allmydata.org/trac/pycryptopp>
Python bindings for the Crypto++ library
More information about the tahoe-dev
mailing list