Bug #3432 segfault on amd64
Submitted: 10 Apr 2004 4:23 Modified: 30 Nov 2004 0:47
Reporter: Antoine Martin Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.0 OS:Linux (Linux (Mandrake64))
Assigned to: Assigned Account CPU Architecture:Any

[10 Apr 2004 4:23] Antoine Martin
Description:
mysqld cannot start, it segfaults 
 
the strace tells me that this happens right after it tries to open 
/lib64/ld-linux-x86-64.so.2 
 
At least the segfault seems to be reliable (same place): 
mysqld[9532]: segfault at 0000000040765aa8 rip 000000004032d5a7 rsp 
0000007fbffff0b0 error 4 
mysqld[9559]: segfault at 0000000040765aa8 rip 000000004032d5a7 rsp 
0000007fbffff0c0 error 4 
mysqld[12881]: segfault at 0000000040765aa8 rip 000000004032d5a7 rsp 
0000007fbffff0c0 error 4 
 

How to repeat:
#> mysqld
[22 May 2004 1:00] Dean Ellis
Are you using one of our 5.0 binaries, or a self-compiled binary?  Also, could you try using a debug binary to see if some additional information is available via that?
[22 May 2004 12:04] Antoine Martin
There is no debug build available on mysql.com for the amd64 platform.

I will install FedoraCore 2 and try again.
[10 Jun 2004 11:08] Antoine Martin
Fedora Core 2 (amd64) had the same problem,

It works on Gentoo 2004.1
(and it is linked to the 64bit libs)
[15 Sep 2004 20:55] Dean Ellis
Does this problem exist with the 5.0.1 dynamic binary?

There was an issue with our statically linked binaries for RH/Fedora servers on the AMD64 platform, and our binaries (from 4.0.21, 4.1.4 and 5.0.1 forward) are dynamically linked to circumvent this.
[22 Oct 2004 14:26] Antoine Martin
[root@localhost root]# mysqld -V
mysqld  Ver 5.0.1-alpha-standard for unknown-linux on x86_64 (Official MySQL RPM)

[root@localhost root]# mysqld
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=0
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 = 217599 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
[22 Oct 2004 14:27] Antoine Martin
I woudn't worry too much about it for now.
I will install Mandrake64 10.1 when it goes gold and we'll see what happens then.
[30 Oct 2004 0:47] MySQL Verification Team
Ok. according with your last post changing the status for your
feedback.

Thanks
[14 Feb 2005 22:54] Bugs System
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".