Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1.8
-
None
-
sol10-64
-
10.1.9-3
Description
Buildbot : http://buildbot.askmonty.org/buildbot/builders/sol10-64/builds/4332
Server log : http://buildbot.askmonty.org/buildbot/builders/sol10-64/builds/4332/steps/test/logs/mysqld.1.err
2015-11-07 1:43:35 1 [Note] InnoDB: Highest supported file format is Barracuda.
|
151107 1:43:36 [ERROR] 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.
|
|
|
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
|
|
|
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.
|
|
|
Server version: 10.1.9-MariaDB-log
|
key_buffer_size=1048576
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=153
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62837 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x0x0
|
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...
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:my_print_stacktrace+0x1e
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:handle_fatal_signal+0x3f4
|
/lib/amd64/libc.so.1:0xdc2e6
|
/lib/amd64/libc.so.1:0xd0bc2
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x14e1ef [ Signal 11 (SEGV)]
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x1c05a8
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x1879c5
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x188102
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x1a1a26
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x1573c5
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x1dd3e3
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/storage/innobase/ha_innodb.so:0x1154c6
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:_Z24ha_initialize_handlertonP13st_plugin_int+0x26c
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:0x42b11c
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:_Z11plugin_initPiPPci+0x9ed
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:0x39558d
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:_Z11mysqld_mainiPPc+0x58f
|
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.9/sql/mysqld:_start+0x6c
|
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.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://dev.mysql.com/doc/mysql/en/crashing.html contains
|
information that should help you find out what is causing the crash.
|
Writing a core file
|
CURRENT_TEST: multi_source.skip_counter
|