Hi Matěj,
I don't really have any knowledge about python-xmlsec and you should
probably reach out to the people who wrote/own it.
Said that, looking at the log file for the crash
(https://gist.github.com/mcepl/43ada31674951bdbd62d8d560575a9f1)
> if (a->error == b->error)
which is about here:
https://github.com/openssl/openssl/blob/17519e2595b5ed8211a7763ff6eb2d6cf47c13cb/crypto/err/err.c#L178
Given that this happens deep inside OpenSSL and the only possible
explanation for the crash is corrupted ERR_STRING_DATA, my first
bet would be on issues with different version of OpenSSL used/loaded
by xmlsec and python at compile/runtime. I would double check the logs
to make sure that same version of all dependencies are used, check
LD_LIBRARY_PATH, ...
My second bet would be on a memory corruption -- I would run valgrind
to see what I can find.
Best,
Aleksey
On 5/21/22 3:21 PM, Matěj Cepl wrote:
Hi,
we are switching openSUSE/Factory to Python 3.10 as default Python
interpreter and one problematic package we have trouble to build is
python-xmlsec (there are surprisingly many packages depending on it).
Details are on https://github.com/mehcode/python-xmlsec/issues/210
Do you have any idea what’s going on?
Best,
Matěj
_______________________________________________
xmlsec mailing list
[email protected]
http://www.aleksey.com/mailman/listinfo/xmlsec
_______________________________________________
xmlsec mailing list
[email protected]
http://www.aleksey.com/mailman/listinfo/xmlsec
