Upon closer examination, I realized the things are not as bad as I thought - if the client aborts connection, the coredump happens only if mysqld was compiled with debugging - otherwise the trouble code is not executed. We will, however, make 3.23.32 release shortly, because of other bad bugs ( although not so terrible as this one). The new Linux binary is already on Sourceforge, the RPMs should be there shortly. I am also building a Solaris 2.7 binary as we speak to test the source distribution ( and to have Solaris binary) - once this is done both will be on Sourceforge. Other binaries will be available on Monday. -- MySQL Development Team __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA <___/ --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
