Here are the results of running valgrind with a debugging build of every relevant package installed:
==241689== Invalid read of size 8
==241689== at 0x53A92E: UnknownInlinedFun (objimpl.h:6)
==241689== by 0x53A92E: _PyObject_New (object.c:534)
==241689== by 0x70D3532: SWIG_Python_newvarlink (selinuxswig_python_wrap.c:
1575)
==241689== by 0x70D3628: SWIG_globals (selinuxswig_python_wrap.c:1605) ==241689== by 0x70D5922: SWIG_Python_DestroyModule (selinuxswig_python_wrap.c:2973)
On 12/04/2025 10:07, Russell Coker wrote:
Here are the results of running valgrind with a debugging build of every relevant package installed:
==241689== Invalid read of size 8
==241689== at 0x53A92E: UnknownInlinedFun (objimpl.h:6)
==241689== by 0x53A92E: _PyObject_New (object.c:534)
==241689== by 0x70D3532: SWIG_Python_newvarlink (selinuxswig_python_wrap.c:
1575)
==241689== by 0x70D3628: SWIG_globals (selinuxswig_python_wrap.c:1605) ==241689== by 0x70D5922: SWIG_Python_DestroyModule (selinuxswig_python_wrap.c:2973)
This looks exactly like an upstream bug in swig [1].
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 59:59:32 |
Calls: | 9,567 |
Calls today: | 1 |
Files: | 13,663 |
Messages: | 6,143,311 |