I see this in my /var/log/mysql/mysql.err when a client connects. This happens only after I compile 3.23.54a or 3.23.55 (didn't test previous versions) like this: USE="static" emerge -u mysql ------------------------------------ mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail key_buffer_size=268431360 record_buffer=1044480 sort_buffer=1048568 max_used_connections=0 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 466539 K bytes of memory Hope that's ok, if not, decrease some variables in the equation Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Stack range sanity check OK, backtrace follows: 0x82d5b28 0x831f2a7 0xffffffff 0x82fd6da 0x82fd3ed 0x8092c88 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolvedtack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... Number of processes running now: 1 mysqld process hanging, pid 7677 - killed Reproducible: Always Steps to Reproduce: 1. emerge mysql: <<USE="static" emerge -u mysql>> 2. restart mysql 3. connect to the server Actual Results: crash ... see error log in previous field Expected Results: no crash Dell 1650: Dual PIII 1,3 GHz - 1G ECC RAM CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe -fomit-frame-pointer" CXXFLAGS="${CFLAGS}" Would be nice if it could be fixed, since mysql-site says building staticly improves performance (and that's exactly what I need)
why not try 3.23.55. i dont have any idea why it dies for you. try asking the mysql people.
sorry, but you'll have to use static builds at your own option.
