Strange SEGV with 4.3.0 #21
Description
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095376
The above Debian bug has started after the transition to swig 4.3, when I recompile libselinux with swig 4.2.1 installed (built from Swig Salsa git) and install all the packaged produced it doesn't crash. It seems that there is something different about Swig 4.3 that causes crashes. This may not be an actual Swig, there is a possibility that it changes memory to expose some other memory related bug.
To reproduce this bug in Debian you have to get the refpolicy source and delete the first patch for refpolicy-2.20250213/Makefile from the patch file debian/patches/2000-hacks and then building refpolicy will fail.
Any suggestions on how to go about debugging this?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095018
Also I believe that the above is related but it's an intermittant bug that I can't reproduce at this time so it may be harder to debug. If the following command causes a SEGV for you then it might be worth debugging, but if not then best to try the Python one even though the process of reproducing it is more complex.
echo "require 'selinux'" | ruby
For Swig developers the long chain of dependencies may make it inconvenient to debug it. I could setup a VM for you with everything needed installed and ready to test if that helps.