Arch Linux

Description:

After recent openssl upgrade python2-m2crypto breaks some python2 apps, for instance, osc, with the following stack trace:

===
free(): invalid size
Transmitting file data
Program received signal SIGABRT, Aborted.
0x00007ffff7837860 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff7837860 in raise () at /usr/lib/libc.so.6
#1 0x00007ffff7838ec9 in abort () at /usr/lib/libc.so.6
#2 0x00007ffff787a437 in __libc_message () at /usr/lib/libc.so.6
#3 0x00007ffff788078b in () at /usr/lib/libc.so.6
#4 0x00007ffff788225c in _int_free () at /usr/lib/libc.so.6
#5 0x00007ffff4440d9d in SSL_SESSION_free () at /usr/lib/libssl.so.1.1
#6 0x00007ffff4441191 in () at /usr/lib/libssl.so.1.1
#7 0x00007ffff444555b in () at /usr/lib/libssl.so.1.1
#8 0x00007ffff44439e6 in () at /usr/lib/libssl.so.1.1
#9 0x00007ffff443be72 in SSL_do_handshake () at /usr/lib/libssl.so.1.1
#10 0x00007fffeead5ea4 in ssl_connect () at /usr/lib/python2.7/site-packages/M2Crypto/_m2crypto.so
#11 0x00007fffeead5fcd in () at /usr/lib/python2.7/site-packages/M2Crypto/_m2crypto.so
#12 0x00007ffff74aae39 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#13 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#14 0x00007ffff74b0cba in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#15 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#16 0x00007ffff74b0cba in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#17 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#18 0x00007ffff74b0cba in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#19 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#20 0x00007ffff74b0cba in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#21 0x00007ffff74ab550 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#22 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#23 0x00007ffff74b07bf in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#24 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#25 0x00007ffff74b07bf in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#26 0x00007ffff74ab550 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#27 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#28 0x00007ffff74b07bf in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
#29 0x00007ffff7505456 in PyEval_EvalCodeEx () at /usr/lib/libpython2.7.so.1.0
#30 0x00007ffff74a111f in function_call.lto_priv () at /usr/lib/libpython2.7.so.1.0
#31 0x00007ffff74ce573 in PyObject_Call () at /usr/lib/libpython2.7.so.1.0
#32 0x00007ffff74ae109 in PyEval_EvalFrameEx () at /usr/lib/libpython2.7.so.1.0
…
===

Updating the package to v0.29.0 fixes this.

Additional info:

Current python2-m2crypto version: 0.27.0
Desired python2-m2crypto version: 0.29.0

Steps to reproduce:

Build some app (e.g., osc for openSUSE Build Service) that works under python2 and uses python2-m2crypto, and it will aborted similar to what happened above.