Re: CVS Current Crash Report (update 02/13)

[Gene ENonymous <yancm@xxxxxxxxxxxxxxxx>]

New cvs version today so I rebuilt. Same issue.
I have updated the debug log:

http://yancm.freeshell.org/tor-cur-021505.txt

Thanks for the suggestion to use tor --version --version.
I have prepended it to the debug log.

I also found the tor.core file and the backtrace gives:
#0  0x10000 in ?? ()
#1  0x4818373b in lh_retrieve () from /usr/lib/libcrypto.so.1
#2  0x48173496 in OBJ_NAME_get () from /usr/lib/libcrypto.so.1
#3  0x4816fce0 in EVP_get_digestbyname () from /usr/lib/libcrypto.so.1
#4  0x48164d01 in ASN1_verify () from /usr/lib/libcrypto.so.1
#5  0x481637d7 in X509_verify () from /usr/lib/libcrypto.so.1
#6  0x481466a5 in X509_verify_cert () from /usr/lib/libcrypto.so.1
#7  0x48146239 in X509_verify_cert () from /usr/lib/libcrypto.so.1
#8  0x480f3d78 in ssl_verify_cert_chain () from /usr/lib/libssl.so.2
#9  0x480eecc8 in ssl3_accept () from /usr/lib/libssl.so.2
#10 0x480ecd49 in ssl3_accept () from /usr/lib/libssl.so.2
#11 0x480fa9f9 in SSL_accept () from /usr/lib/libssl.so.2
#12 0x808d217 in tor_tls_handshake (tls=0x813c780) at tortls.c:515
#13 0x8062791 in connection_tls_continue_handshake (conn=0x813d600)
    at connection_or.c:290
#14 0x805c45a in connection_read_to_buf (conn=0x813d600, 
    max_to_read=0xbfbfda44) at connection.c:955
#15 0x805c30a in connection_handle_read (conn=0x813d600) at connection.c:897
#16 0x806ea99 in conn_read_callback (fd=23, event=2, _conn=0x813d600)
    at main.c:342
#17 0x808ebc7 in event_process_active ()
#18 0x808ed88 in event_loop ()
#19 0x808ebf0 in event_dispatch ()
#20 0x806f971 in do_main_loop () at main.c:1027
#21 0x8070469 in tor_main (argc=1, argv=0xbfbfdba8) at main.c:1652
#22 0x808105c in main (argc=1, argv=0xbfbfdba8) at tor_main.c:18
#23 0x804bf40 in ___start ()


> I'm running NetBSD 1.6.2(Stable) on a P-166 w/80M Ram
>
> I do not see any explanation for the crash in this file or the warnings
> file I typically capture. What ever it is it seems to stop abruptly.