(I made this an answer because characters are limited in comments)
NOTE: As Samuel made me remark buster should install 8.6. That is to say your segfault does not seem to be related to the sagemath package in buster. How did you launch Sage? Could you try $ which sage?
I can not reproduce the segmentation fault in docker (after pulling the buster image and installing sagemath from apt). Note that the version they ship is 8.6 which is quite old and you did not run this version. One possibility is that you have libraries that you installed manually (eg in /usr/local) that create some undesired interactions. To check linking from sage you could do $ ldd /usr/lib/python2.7/dist-packages/sage/rings/polynomial/polynomial_zz_pex.x86_64-linux-gnu.so. In docker I got
It seems I installed sagemath from testing (i.e. apt-get install -t testing sagemath). Sorry for the confusion. I realize this is not a recommended method of installation.
Welcome to Ask Sage! Thanks for your question.
Not seeing this on macOS with SageMah 9.3.rc2, nor on SageCell currently at Sage 9.2.
What operating system? How was Sage installed?
Debian Buster, installed using
sudo apt-get install sagemath
.It's not reproducible in Sage compiled from source:
I guess there's something broken about the Debian package or the libraries it uses.
The OS-packaged sage is using Python 3.9.2, if that helps. Anything I can do to help debug the package?
Correction: I actually installed from testing; see comment below.