$ PYTHONDEVMODE=1 python boom.py
Debug memory block at address p=0x560098099e80: API '!'
0 bytes originally requested
The 7 pad bytes at p-7 are not all FORBIDDENBYTE (0xfd):
at p-7: 0x00 *** OUCH
at p-6: 0x00 *** OUCH
at p-5: 0x00 *** OUCH
at p-4: 0x00 *** OUCH
at p-3: 0x00 *** OUCH
at p-2: 0x00 *** OUCH
at p-1: 0x00 *** OUCH
Because memory is corrupted at the start, the count of bytes requested
may be bogus, and checking the trailing pad bytes may segfault.
The 8 pad bytes at tail=0x560098099e80 are not all FORBIDDENBYTE (0xfd):
at tail+0: 0x10 *** OUCH
at tail+1: 0x29 *** OUCH
at tail+2: 0x77 *** OUCH
at tail+3: 0x7b *** OUCH
at tail+4: 0x92 *** OUCH
at tail+5: 0x7f *** OUCH
at tail+6: 0x00 *** OUCH
at tail+7: 0x00 *** OUCH
Enable tracemalloc to get the memory block allocation traceback
Fatal Python error: _PyMem_DebugRawFree: bad ID: Allocated using API '!', verified using API 'm'
Python runtime state: initialized
Current thread 0x00007f927bfd1000 (most recent call first):
File "/usr/local/lib/python3.10/dist-packages/onelogin/saml2/utils.py", line 763 in add_sign
File "/usr/local/lib/python3.10/dist-packages/onelogin/saml2/metadata.py", line 216 in sign_metadata
File "/usr/local/lib/python3.10/dist-packages/onelogin/saml2/settings.py", line 740 in get_sp_metadata
File "boom.py", line 128 in <module>
Extension modules: lxml._elementpath, lxml.etree, xmlsec (total: 3)
Aborted
Environment
I'm running on Ubuntu 22.04 with system python 3.10.6 and python3-saml 1.15.0.
When running .get_sp_metadata() with the additional runtime checks of the Python Development Mode the interpreter crashes with a segmentation fault.
Expected output
Observed output
Environment
I'm running on Ubuntu 22.04 with system python 3.10.6 and python3-saml 1.15.0.
pip list
boom.py: