MySQL Bugs: #4459: mysqld 4.0.20 (ICC compiled by mysql.com) quits with signal 11

Bug #4459	mysqld 4.0.20 (ICC compiled by mysql.com) quits with signal 11
Submitted:	8 Jul 2004 11:44	Modified:	28 Oct 2004 2:59
Reporter:	[ name withheld ]	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	mysql-4.0.20-standard (ICC)	OS:	Vanilla 2.4.26/gentoo x86 2004.1
Assigned to:	Matthew Lord	CPU Architecture:	Any

Description:
I installed mysql 4.0.20 (ICC Intel Compiler compiled mysql,
 compiled by mysql.com) and when starting mysqld it immediately exits
 with signal 11 and wrote this into mysqld-log:

040703 23:24:30  mysqld started
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=0x84a4d10
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=0xf0efeeed, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0xf0efeeed, stack_bottom=0xc0000000,
thread_stack=196608, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xecebeae9  is invalid pointer
thd->thread_id=139089296
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.
040703 23:24:30  mysqld ended

>Release: mysql-4.0.20-standard (Official MySQL-standard binary)

>C compiler:    8.0
>C++ compiler:  8.0
>Environment: gentoo linux, intel mainboard, pentium 4, IDE HDD, 1024 MB RAM

System: Linux server5 2.4.26 #2 SMP Do Jun 24 20:00:00 CEST 2004 i686
Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
Architecture: i686

Some paths:  /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
/usr/bin/cc
GCC: Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/specs
Configured with:
/var/tmp/portage/gcc-3.3.2-r5/work/gcc-3.3.2/configure --prefix=/usr --bindi
r=/usr/i686-pc-linux-gnu/gcc-bin/3.3 --includedir=/usr/lib/gcc-lib/i686-pc-l
inux-gnu/3.3.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3 -
-mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.3/man --infodir=/usr/share/g
cc-data/i686-pc-linux-gnu/3.3/info --enable-shared --host=i686-pc-linux-gnu 
--target=i686-pc-linux-gnu --with-system-zlib --enable-languages=c,c++,f77,o
bjc --enable-threads=posix --enable-long-long --disable-checking --enable-cs
tdio=stdio --enable-clocale=generic --enable-__cxa_atexit --enable-version-s
pecific-runtime-libs --with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-g
nu/3.3.2/include/g++-v3 --with-local-prefix=/usr/local --enable-shared --ena
ble-nls --without-included-gettext --disable-multilib
Thread model: posix
gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
Compilation info: CC='icc'  CFLAGS='-O3 -unroll2 -ip -mp -no-gcc -restrict'
CXX='icc'  CXXFLAGS='-O3 -unroll2 -ip -mp -no-gcc -restrict'  LDFLAGS=''
ASFLAGS=''
LIBC:
lrwxrwxrwx    1 root     root           13 Jun 24 18:09 /lib/libc.so.6 ->
libc-2.3.2.so
-rwxr-xr-x    1 root     root      1272572 Apr 13 07:32 /lib/libc-2.3.2.so
-rw-r--r--    1 root     root      2707526 Apr 13 07:32 /usr/lib/libc.a
-rwxr-xr-x    1 root     root          204 Apr 13 07:32 /usr/lib/libc.so
Configure command: ./configure '--prefix=/usr/local/mysql'
'--localstatedir=/usr/local/mysql/data' '--libexecdir=/usr/local/mysql/bin'
'--with-comment=Official MySQL-standard binary'
'--with-extra-charsets=complex' '--with-server-suffix=-standard'
'--enable-thread-safe-client' '--enable-local-infile' '--enable-assembler'
'--disable-shared' '--with-client-ldflags=-all-static'
'--with-mysqld-ldflags=-all-static' '--with-embedded-server' '--with-innodb'
'CC=icc' 'CFLAGS=-O3 -unroll2 -ip -mp -no-gcc -restrict'
'CXXFLAGS=-O3 -unroll2 -ip -mp -no-gcc -restrict' 'CXX=icc'

How to repeat:
 I just need to try to start mysqld.

Suggested fix:
Sorry, no idea.

I have same issue on Debian platform with 2.4.26 kernel and mysql-standart-4.0.20 (ICC) and mysql-debug-4.0.20 (ICC).
040720 00:51:58 mysqld started
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=0x8514270
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:
Stack trace seems successful - bottom reached
Please read http://www.mysql.com/doc/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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x54454500 is invalid pointer
thd->thread_id=1919639395
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.
040720 00:51:58 mysqld ended

Hi,

I was not able to repeat this on a RH 9 box:

Linux booty 2.4.21 #12 SMP Thu Aug 14 00:49:40 EDT 2003 i686 i686 i386 GNU/Linux

Would you be able to provide your /etc/my.cnf file?  Can you repeat this on your box when using 
--no-defaults? 

Best Regards

Yes, with --no-defaults I had the same result.
How may I help you to reproduce this?

Can you please check, if the 4.0.21 binary shows the same behaviour? We have now changed from static to dynamic linking for these.

Probably a duplicate of bug#5567?

I cannot repeat this with 4.0.21.  Starting with 4.0.21 we are linking this dynamically as the static 
linking with icc was very problematic.

You will also need the additional ICC libraries which are linked to from the downloads page:
http://dev.mysql.com/downloads/os-linux.html

Best Regards