Don't have that platform to test on. However from the stack dump:
#0 0x0000000800d6e466 in memcpy () from /lib/libc.so.6
#1 0x0000000800770a5e in asn1_ex_i2c (pval=0x61d708,
cout=0x61d708
"IxMVoXDTA5MDcxMjE2MjIxMVowRDELMAkGA1UEBhMCSFUx\nETAPBgNVBAgTCEJ1ZGFwZXN0MRQwEgYDVQQKEwtHb3YtQ0EgTHRkLjEMMAoGA1UE\nAxMDY2ExMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDOfD7M8XohD/fO5Uwt\nnEB9IzrcbhUDmZ/VvV/9/ZS"...,
putype=0x80, it=0x10) at tasn_enc.c:688
^^^^^^^
That value of 'it' is obviously dodgy. Going up a level:
#2 0x0000000800770c9d in ASN1_item_ex_i2d (pval=0x61b828,
out=0x7fffffffc2e0,
it=0x8008eef00, tag=4, aclass=0) at tasn_enc.c:551
That *may* be OK.
#3 0x0000000800771343 in asn1_template_ex_i2d (pval=0x61b828,
out=0x7fffffffc2e0, tt=0x8008f5cc8, tag=16, iclass=128) at
tasn_enc.c:413
And the same here. So if you print out *tt from frame #3 and *it from
frame #2 it should be possible to determine which bit of the structure
it is processing.
Assuming the whole thing isn't a compiler bug.
Steve.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
