MySQL Bugs: #39930: mysqld gets SIGBUS on SPARC

Bug #39930	mysqld gets SIGBUS on SPARC
Submitted:	8 Oct 2008 13:20	Modified:	20 Feb 2009 20:44
Reporter:	Daniel Fischer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	mysql-6.0 bzr	OS:	Solaris (8,9,10 on SPARC)
Assigned to:		CPU Architecture:	Any

Description:
As of revision mats@sun.com-20081001120926-4rp1ye3zz30yrx02, mysqld compiled from the mysql-6.0 branch gets SIGBUS on startup on Solaris SPARC platforms in non-debug builds.

+ perl mysql-test-run.pl --timer --force --comment=n_mix --mysqld=--binlog-format=mixed
Requesting build thread... got 200
Logging: mysql-test-run.pl --timer --force --comment=n_mix --mysqld=--binlog-format=mixed
081008 12:02:32 - mysqld got signal 10 ;
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=0
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 330140 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

How to repeat:
Build a non-debug binary from 6.0 on Solaris on SPARC and try to run it.

Example configuration for Solaris 10 SPARC 64-bit:

+ CFLAGS='-g -O2 -Xa -xstrconst -mt -D_FORTEC_ -m64'
+ CXXFLAGS='-g -O2 -noex -mt -D_FORTEC_ -m64'
+ ASFLAGS='-g -m64'
+ LDFLAGS='-g -m64'
+ export CFLAGS
+ export CXXFLAGS
+ export ASFLAGS
+ export LDFLAGS
+ ./configure --enable-thread-safe-client --enable-local-infile --with-pic --with-client-ldflags=-static --with-mysqld-ldflags=-static --with-zlib-dir=bundled --without-ndb-debug --with-big-tables --with-ssl --with-readline --with-embedded-server --with-archive-storage-engine --with-blackhole-storage-engine --with-csv-storage-engine --with-example-storage-engine --with-federated-storage-engine --with-partition --with-extra-charsets=all --with-innodb --with-ndbcluster --with-libevent --with-falcon

Suggested fix:
Look for unaligned memory access.

Thank you for the report.

Which box and compiler did you use?

Compiler was Sun Studio 12 on Solaris 10 U5.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Do we still have this problem with 6.0.9?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".