On 10/12/2025 08:05, Otto Kekäläinen wrote:
I ran a detailed stack trace on stadler.debian.net and posted it in upstream Jira at https://jira.mariadb.org/browse/MDEV-36670 in hopes upstream could gain valuable insights from reading it. I also posted there my notes on the exact steps I ran on stadler to build MariaDB and run mariadb-test-run in case someone wants to repeat it. I can also post the same thing here if you think it is valuable for Debian bug tracking.
I'm clueless about the initial stack trace with the SIGUSR1s, but the SIGILL one you posted further below seems very odd and somewhat unrelated, but still serious. _sparcv9_random is from OpenSSL, and while I can't find the exact version, I think it matches this piece of code: https://github.com/openssl/openssl/blob/0e9725bcb90770d967351b977407b174bbd91869/crypto/sparccpuid.S#L347-L353 Not sure if there's an issue with the hardcoded opcode, or perhaps an incorrectly identified CPU type, but the .size line seems off. Shouldn't this read ".size _sparcv9_random,.-_sparcv9_random" instead?
