I was following: - https://dev.mysql.com/doc/refman/8.0/en/using-gdb-on-mysqld.html I - https://dev.mysql.com/doc/refman/8.0/en/crashing.html
Which mostly comes down to: $ apt source mysql-server-8.0 $ apt install gdb mysql-server-core-8.0-dbgsym libc6-dbg libstdc++6-dbgsym $ sudo gdb /usr/sbin/mysqld (gdb) run --skip-stack-trace --gdb --core-file --general-log --general-log-file --verbose --innodb-read-only --help --debug To be clear - in a normal working environment that would not even start the server for real - it would initialize a bit and then report on the used and possible config options. For comparison in a similar environment I'll also use 8.0.23-0ubuntu0.20.04.1 in Focal. Hoping that this might help to differentiate the noise from data. But since things work there I'll need to find which function to break on ... I'll attach an initial backtrace here ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915275 Title: mysql-8.0 regressed on riscv64 due to new glibc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1915275/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
