Hello.
You have links in MySQL message which you should follow. Resolve the stack trace. I suggest you to switch to 4.1.11. If you are able to make a repeatable test case you may report a bug. Does the problem remain with a debug package? >Hi, >We tried to install mysql-max-4.1.10a-pc-linux-gnu-i686 on linux 2.4.30 >with redhat es 3.0 > > When I executed the mysql_install_db script , I have these errors: > > [EMAIL PROTECTED] mysql]# scripts/mysql_install_db --user=mysql > Installing all prepared tables > 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=8388600 > read_buffer_size=131072 > max_used_connections=0 > max_connections=100 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + > sort_buffer_size)*max_connections = 225791 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=(nil) > 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... > Cannot determine thread, fp=0x40a4c77c, backtrace may not be > correct. > Stack range sanity check OK, backtrace follows: > 0x8136a43 > 0x40054e58 > (nil) > New value of fp=(nil) failed sanity check, terminating stack trace! > Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html > and follow > instructions on how to resolve the stack trace. Resolved > stack trace is much more helpful in diagnosing the problem, so > please do > resolve it > The manual page at http://www.mysql.com/doc/en/Crashing.html > contains > information that should help you find out what is causing the crash. > > > Can someone help me ? > > > David M. > >"Marois, David" <[EMAIL PROTECTED]> wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
