strange crash in SSL code while opening some documents

Markus Mohrhard markus.mohrhard at
Sat Jun 8 05:27:04 PDT 2013


so it seems that on my computer with gcc 4.8 and linux binutils
2.23.51 I have some problems with our code for SSL handling.

With each document trying to connect to a https website I get a crash
with the following backtrace:

#0  0x00007ffff75cb207 in __strncmp_sse42 () from /lib64/
#1  0x00007fffba1b0f90 in ssl_cipher_process_rulestr
(rule_str=0x7fffba1f27b8 "AES:ALL:!aNULL:!eNULL:+RC4:@STRENGTH",
co_list=0x1dfd950, head_p=0x7fffffff3640, tail_p=0x7fffffff3638,
    at ssl_ciph.c:876
#2  0x00007fffba1b157e in ssl_create_cipher_list
(ssl_method=0x7fffba4447e0 <SSLv23_client_method_data.13759>,
cipher_list=0x1dfd318, cipher_list_by_id=0x1dfd320, rule_str=
    0x7fffba1f27b8 "AES:ALL:!aNULL:!eNULL:+RC4:@STRENGTH") at ssl_ciph.c:1040
#3  0x00007fffba1aa965 in SSL_CTX_new (meth=0x7fffba4447e0
<SSLv23_client_method_data.13759>) at ssl_lib.c:1534
#4  0x00007fffba0dd9bd in ne_ssl_context_create (mode=0) at
#5  0x00007fffba0d4621 in ne_session_create (scheme=0x7fffcc169618
"https", hostname=0x7fffcc159350 "", port=443)
    at /devel/libo/libo3/workdir/unxlngx6/UnpackedTarball/neon/src/ne_session.c:176
#6  0x00007fffba48eef7 in webdav_ucp::NeonSession::Init
(this=0x1de7b70) at
#7  0x00007fffba48f40e in webdav_ucp::NeonSession::UsesProxy
(this=0x1de7b70) at
#8  0x00007fffba476a31 in webdav_ucp::DAVResourceAccess::getRequestURI
(this=0x1de7830) at
#9  0x00007fffba472f28 in webdav_ucp::DAVResourceAccess::PROPFIND
(this=0x1de7830, nDepth=webdav_ucp::DAVZERO,
rPropertyNames=std::__debug::vector of length 4, capacity 4 = {...},
    rResources=std::__debug::vector of length 0, capacity 0,
xEnv=uno::Reference to (ucbhelper::CommandEnvironment *)
0x7fffcc158678) at

So I debugged this and it looks like this might be a compile or
linking problem because stepping through the code does not show
anything going wrong but at some point the values seem to no longer
make sense.

Can someone else with gcc 4.8 and linux current binutils check if he
sees the same problem? I think the new Fedora 19 uses the same
configuration so anyone running this and having a current master build
should be able to check it. A possible test document for this is
ooo121280 or lp990868.


More information about the LibreOffice mailing list