BIND-9.6.1-P2 t_dst test failing on latest solaris development release.
Stacey Jonathan Marshall
Stacey.Marshall at Sun.COM
Fri Dec 4 16:32:00 UTC 2009
I'm seeing an issue with BIND-9.6.1-P2 t_dst test on latest Solaris builds,
works fine with OpenSolaris 2009.06 and Solaris 10.
I'm trying the test on some older builds but wondered if you fine folks
had any thoughts.
# cd /var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst
# ./t_dst -b . -q 1800 -a
S:/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst/.libs/t_dst:Friday 04 December 15:24:24 2009
T:dst:1:A
A:the dst module provides the capability to generate, store and retrieve public and private keys, sign and verify data using the RSA, DSA and MD5 algorithms, and compute Diffie-Hellman shared secrets.
I:testing use of stored keys [1]
I:testing use of stored keys [2]
I:testing use of stored keys [3]
I:testing use of stored keys [4]
I:testing use of generated keys
R:PASS
T:dst:2:A
A:the dst module provides the capability to verify data signed with the RSA and DSA algorithms
I:testing t2_data_1, t2_dsasig, test., 23616, DST_ALG_DSA, ISC_R_SUCCESS
I:testing t2_data_1, t2_rsasig, test., 54622, DST_ALG_RSAMD5, ISC_R_SUCCESS
I:testing t2_data_1, t2_dsasig, test., 54622, DST_ALG_RSAMD5, !ISC_R_SUCCESS
I:testing t2_data_2, t2_dsasig, test., 23616, DST_ALG_DSA, !ISC_R_SUCCESS
mem.c:322: INSIST(dl != 0) failed.
I:the test case caused exception 6
R:UNRESOLVED
E:/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst/.libs/t_dst:Friday 04 December 15:24:32 2009
# pstack core
core 'core' of 27884: /var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst/.libs/t_
fe8c73b8 _lwp_kill (6, ffffffef, ffffffec, 6, 5, 6) + 8
fe84e340 abort (0, fe956000, 6, 1, fe957880, 0) + 108
fef18640 default_callback (fef85758, fef8a764, 2, fef8a764, ffffffe0, 115101) + d0
fef348f4 delete_trace_entry (b5b98, 1150e8, 18, ff2db9fc, 92, 0) + 4a4
fef3a424 isc__mem_free (b5b98, 1150e8, ff2db9fc, 92, 0, 0) + 38c
ff261628 mem_free (1150e8, 0, 0, 0, 0, 1257f0) + d0
fed5e85c CRYPTO_free (508, 400, 8, fee88fe8, 430, 400) + 50
fedd3d7c pk11_active_delete (13b778, 2, 718, 1cc00, fee84000, 400) + a8
fedd08c4 pk11_destroy_dsa_object_pub (13d8b8, fee84000, 13d8b8, 800, ffff0000, 13b778) + 58
fedd6a74 pk11_dsa_do_verify (ffbfeb7c, 14, 13d8b8, 91f40, afc28, a7) + 1cc
ff2647ac openssldsa_verify (d4a18, ffbfee88, ff2d9708, f9, feeb2a00, 0) + 134
ff254414 dst_context_verify (d4a18, ffbfee88, ffbfec8c, 149a9, 27bf4, 149a8) + 1b4
00013d78 t2_sigchk (27bc8, 27bd2, 27bdc, 5c40, 3, 6000000) + 5b8
00014204 t2_vfy (27bf4, ffbff210, fe95a3c0, fe956000, feeb2a00, 0) + 3ac
ff3730c8 t_eval (14b24, 13e58, 6, 14b20, 14bf8, 0) + 128
00014324 t2 (0, 1, 0, feeb2a00, fe95a480, fe95a3c0) + 7c
ff371e38 main (6, ffbff484, ffbff4a0, 25000, 0, feeb0180) + 880
000118d8 _start (0, 0, 0, 0, 0, 0) + 108
# pldd core
core 'core' of 27884: /var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst/.libs/t_
/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/lib/tests/.libs/libt_api.so.0.0.0
/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/lib/dns/.libs/libdns.so.53.0.0
/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/lib/isc/.libs/libisc.so.50.1.1
/lib/libcrypto.so.0.9.8
/lib/libscf.so.1
/lib/libxml2.so.2
/lib/libz.so.1
/lib/libpthread.so.1
/lib/libm.so.2
/lib/libsocket.so.1
/lib/libnsl.so.1
/lib/libc.so.1
/platform/sun4u/lib/libc_psr.so.1
/usr/lib/libpkcs11.so.1
/lib/libcryptoutil.so.1
/lib/libuutil.so.1
/lib/libgen.so.1
/usr/lib/security/pkcs11_kernel.so.1
/lib/libmd.so.1
/platform/sun4u/lib/libmd_psr.so.1
/usr/lib/security/pkcs11_softtoken.so.1
/usr/lib/libsoftcrypto.so.1
/usr/platform/sun4u/lib/libsoftcrypto_psr.so.1
/usr/lib/libldap.so.5
/usr/lib/libsasl.so.1
/usr/lib/mps/libplc4.so
/usr/lib/mps/libnspr4.so
/lib/librt.so.1
/lib/libdl.so.1
/usr/lib/mps/cpu/sparcv8plus/libnspr_flt4.so
/usr/lib/mps/libssl3.so
/usr/lib/mps/libnss3.so
/usr/lib/mps/libnssutil3.so
/lib/libthread.so.1
/usr/lib/mps/libplds4.so
/lib/libresolv.so.2
/lib/libmp.so.2
Digging around I find that some memory debugging features exist. Some
commands such as named and dig have command line options to enable this
but alas for the testing we have to edit a file:
# cd /var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/lib/tests
# mv t_api.c t_api.orig.c
# sed 's/ISC_MEM_DEBUGRECORD/ISC_MEM_DEBUGRECORD | ISC_MEM_DEBUGTRACE/' \
> t_api.orig.c > t_api.c
# diff t_api.orig.c t_api.c
125c125
< isc_mem_debugging = ISC_MEM_DEBUGRECORD;
---
> isc_mem_debugging = ISC_MEM_DEBUGRECORD | ISC_MEM_DEBUGTRACE;
# make
...
# cd -
/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst
# ./t_dst -b . -q 1800 -a >results 2>&1; tail results
add afc28 size 16 file openssl_link.c line 139 mctx b5b98
add 115020 size 28 file openssl_link.c line 139 mctx b5b98
add 114f08 size 28 file openssl_link.c line 139 mctx b5b98
add 114f58 size 28 file openssl_link.c line 139 mctx b5b98
add 114f80 size 28 file openssl_link.c line 139 mctx b5b98
del 1150e8 size 24 file openssl_link.c line 146 mctx b5b98
mem.c:322: INSIST(dl != 0) failed.
I:the test case caused exception 6
R:UNRESOLVED
E:/var/tmp/bind_nv/usr/src/cmd/bind/bind-9.6.1-P2/bin/tests/dst/.libs/t_dst:Friday 04 December 15:34:34 2009
The trace comes from lib/isc/mem.c, it seems to indicate that there was
no block assigned from "mctx b5b98".
-- Stace
More information about the bind-workers
mailing list