9 messages in com.mysql.lists.bugs64bit mysqld signal 10 (bus error) on...
FromSent OnAttachments
Jörg Prante23 Aug 2002 17:53 
Michael Widenius25 Aug 2002 11:24 
Jörg Prante25 Aug 2002 15:26 
Michael Widenius26 Aug 2002 05:36 
Heikki Tuuri26 Aug 2002 11:08 
Jörg Prante26 Aug 2002 15:16 
Jörg Prante26 Aug 2002 15:25 
Heikki Tuuri27 Aug 2002 01:29 
Sinisa Milivojevic29 Aug 2002 04:31 
Subject:64bit mysqld signal 10 (bus error) on sparcv9-sun-solaris2 and gcc 3.2
From:Michael Widenius (mon@mysql.com)
Date:08/25/2002 11:24:19 AM
List:com.mysql.lists.bugs

Hi!

"Jörg" == Jörg Prante <<joer@netcologne.de> (by way of Jörg Prante
<joer@netcologne.de>)> writes:

Jörg> MySQL 4.0.2-alpha built with gcc 3.2-64bit in 64 bit mode on a SunBlade Jörg> 1000 under Solaris 8 fails at running mysqld.

Jörg> Everything works fine (I can use mysql client and remote connect to
another Jörg> mysqld, and mysql_db_install script works fine too) but not mysqld. It
fails Jörg> immediately with signal 10 (bus error) when I try 'mysqld_safe &'. No core Jörg> dump. '/tmp/mysql.sock' is created but size is 0 (zero) bytes after
failure.

I think this is an indication that gcc 3.2-64 bit can't yet produce a 64 bit thread safe binary.

The reasons for the above assumption is that we know that MySQL 4.0 is 64 bit clean as it works without any problems on Linux-Alpha, Linux-Itanium and Solaris 2.8, the last one compiled with Suns 64 bit compiler.

The only way to fix this is to compile MySQL with debugging (configure --with-debug) and run mysqld under a debugger to find out what's going wrong.

<cut>

Jörg> I checked it and I'm quite sure there is no 32bit library involved. Jörg> 'bin/mysql' works, but not 'bin/mysqld_safe &'. If you need more info,
please Jörg> email me. I would appreciate it to get that 64bit mysqld beast running.

Please read the 'debugging mysqld under gdb' manual entry to get more information how to proceed.

Regards, Monty