#0  0x0000000000000000 in ?? ()
#1  0x0000086c5482561e in tor_free_ () from /usr/local/bin/tor
#2  0x0000086c548257d0 in tor_free_ () from /usr/local/bin/tor
#3  0x0000086eeb0f48cb in ssl3_get_client_hello (s=0x86f47efe000) at 
/usr/src/lib/libssl/ssl/../../libssl/src/ssl/s3_srvr.c:1119
#4  0x0000086eeb0f5505 in ssl3_accept (s=0x86f47efe000) at 
/usr/src/lib/libssl/ssl/../../libssl/src/ssl/s3_srvr.c:346
#5  0x0000086eeb0ed574 in ssl23_get_client_hello (s=0x86f47efe000) at 
/usr/src/lib/libssl/ssl/../../libssl/src/ssl/s23_srvr.c:573
#6  0x0000086eeb0edd96 in ssl23_accept (s=0x86f47efe000) at 
/usr/src/lib/libssl/ssl/../../libssl/src/ssl/s23_srvr.c:232
#7  0x0000086c54825b57 in tor_free_ () from /usr/local/bin/tor
#8  0x0000086c547c203d in compare_vote_routerstatus_entries () from 
/usr/local/bin/tor
#9  0x0000086c547c24f0 in compare_vote_routerstatus_entries () from 
/usr/local/bin/tor
#10 0x0000086c547b2b8e in compare_vote_routerstatus_entries () from 
/usr/local/bin/tor
#11 0x0000086c547b3986 in compare_vote_routerstatus_entries () from 
/usr/local/bin/tor
#12 0x0000086c54714181 in ?? () from /usr/local/bin/tor
#13 0x0000086e9e99c198 in event_base_loop (base=0x86ecbd78c00, flags=Variable 
"flags" is not available.
) at /usr/src/lib/libevent/event.c:404
#14 0x0000086c54711da2 in ?? () from /usr/local/bin/tor
#15 0x0000086c54712155 in ?? () from /usr/local/bin/tor
#16 0x0000086c54710311 in ?? () from /usr/local/bin/tor
#17 0x0000000000000000 in ?? ()



Monday, September 29, 2014, 11:12:38 AM, you wrote:

> You can start a process directly from gdb, or you can attach gdb to
> a running process before it crashes and 'continue', then obtain a
> backtrace after the crash. Without more information (specifically a
> backtrace) there isn't much anyone can do to help.

> "its not problem of tor, nobody reported about the problem
> somewhere else" - this doesn't make sense. Buggy programs are more
> likely to crash quickly on OpenBSD than other OS (reasons include
> free() overwriting the start of freed memory by default and stricter
> mutex checks). These would still be bugs in the program not the OS.

Reply via email to