Re: [Srtp-development] bus error on sparc

[Daniel P. <da...@po...>]

On 18/07/13 21:25, Michael Jerris wrote:
> If that fixed it.. then the issue is the missing def for FORCE_64BIT_ALIGN.  Also of note, that pad shouldn't be there anymore after algorithm was added I suspect, as it always serves the same purpose.
> 

Ok, I've just manually checked that it works on our sparc machine
https://db.debian.org/machines.cgi?host=smetana

I did this test in the build tree from the Debian source package
http://anonscm.debian.org/gitweb/?p=collab-maint/srtp.git;a=summary

./configure CPPFLAGS='-DFORCE_64BIT_ALIGN' && make runtest


No more bus error, it proceeds much further, but it still fails with an
error status:


$ make runtest
Build done. Please run 'make runtest' to run self tests.
running libsrtp test applications...
crypto/test/cipher_driver -v >/dev/null
crypto/test/kernel_driver -v >/dev/null
test/rdbx_driver -v >/dev/null
test/srtp_driver -v >/dev/null
test/roc_driver -v >/dev/null
test/replay_driver -v >/dev/null
test/dtls_srtp_driver >/dev/null
cd test; /home/pocock/ws/srtp/srtp/test/rtpw_test.sh >/dev/null	
libsrtp test applications passed.
make -C crypto runtest
make[1]: Entering directory `/home/pocock/ws/srtp/srtp/crypto'
test/env # print out information on the build environment
CPU set to big-endian			(WORDS_BIGENDIAN == 1)
CPU set to RISC				(CPU_RISC == 1)
using native 64-bit type		(NO_64_BIT_MATH == 0)
using stdout for error reporting	(ERR_REPORTING_STDOUT == 1)
using /dev/urandom as a random source	(DEV_URANDOM == /dev/urandom)
running libcryptomodule test applications...
test `test/aes_calc 000102030405060708090a0b0c0d0e0f
00112233445566778899aabbccddeeff` = 69c4e0d86a7b0430d8cdb78070b4c55a
test `test/aes_calc
000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
00112233445566778899aabbccddeeff` = 8ea2b7ca516745bfeafc49904b496089
test/cipher_driver -v >/dev/null
test/datatypes_driver -v >/dev/null
test/stat_driver >/dev/null
make[1]: *** [runtest] Error 1
make[1]: Leaving directory `/home/pocock/ws/srtp/srtp/crypto'
make: *** [runtest] Error 2



although running it again with

  make runtest

it finishes successfully the second time.

I've now added FORCE_64BIT_ALIGN to the debian/rules file in our source
package - should this be used on any other 64 bit platforms?

The Debian package still doesn't build completely though, it appears to
fail the same way as the manual attempt above.  If I execute "make
runtest" immediately after it fails, then it runs the tests again and it
is successful.

Commenting out test/stat_driver in crypto/Makefile I was able to make it
run successfully in a single run

Then I cleaned the source tree again but instead of commenting out
test/stat_driver I just removed the redirect to /dev/null, now I get this:

test/stat_driver
statistical tests driver
running stat_tests on all-null buffer, expecting failure
monobit 11
poker   11
runs    11
running stat_tests on rand(), expecting success
monobit 0
poker   0
runs    0
running stat_tests on AES-128-ICM, expecting success
error (code 6)