MySQL Bugs: #28099: mysqldump leads to "bus error (core dumped)"

Bug #28099	mysqldump leads to "bus error (core dumped)"
Submitted:	25 Apr 2007 15:22	Modified:	10 Jun 2007 10:58
Reporter:	Steve Nguyen	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	Ver 14.12 Distrib 5.0.27	OS:	Solaris (5.9)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Installed MySQL 

./mysql --version
./mysql  Ver 14.12 Distrib 5.0.27, for sun-solaris2.9 (sparc) using  EditLine wrapper 

Server type

bash-2.05# uname -a
SunOS tx2suitedb2 5.9 Generic_112233-10 sun4u sparc SUNW,UltraAX-i2
_____________________________________
I next ran the following command: 

mysqldump --master-data --all-databases -h SomeHostIChose -u root -p > /downloads/mysql_backup_4-23-2007
_____________________________________
I get the following error after inputting my password.

Enter password:
Bus Error (core dumped)

How to repeat:
Installed MySQL 

./mysql --version
./mysql  Ver 14.12 Distrib 5.0.27, for sun-solaris2.9 (sparc) using  EditLine wrapper 

Server type

bash-2.05# uname -a
SunOS tx2suitedb2 5.9 Generic_112233-10 sun4u sparc SUNW,UltraAX-i2
_____________________________________
I next ran the following command: 

mysqldump --master-data --all-databases -h SomeHostIChose -u root -p > /downloads/mysql_backup_4-23-2007
_____________________________________
I get the following error after inputting my password.

Enter password:
Bus Error (core dumped)

Core Dumped File (Will need to unzip)

Virus scan engine found a threat. This file might be infected. Attachment: core.zip (application/zip, text), 200.44 KiB.

This is a replication/backup issue.

Somewhere in between installing MySQL and dumping its content, I populated it with some databases and data.

I just gave the remote mysqldump example. I essentially attempted to dump locally and remotely from off server. So server X was where I installed it. Ran that mysqldump.. etc... command on server X and on server Y, attempting to get the data from Y.

Thank you for the report.

Please provide mysqldump you used to create core file.

Also try with new 5.0.37 version, because version 5.0.27 is quite old and problem can be solved already.

As per your request, see below command I used for mysqldump

mysqldump -u root -p suite --password='bob2' -h tx2suitedb1 > backkup5_4_2007.sql

I might have misunderstood.

Are you asking for the binary of mysqldump?

>I might have misunderstood.
>Are you asking for the binary of mysqldump?

Yes, I am asking for the binary of mysqldump. We need to have it to have possibility to analyze the core file.

mysqldump binary

Attachment: mysqldump (application/octet-stream, text), 84.82 KiB.

See files section for mysqldump binary.

-thx

Thank you for the uploaded file.

Core file doesn't contain much useful information: just note about access to undefined address.

Please try with mysqldump from current 5.0.41 MySQL pacakage accessible from http://dev.mysql.com/downloads/mysql/5.0.html and if you can repeat error, indicate if you always get such error or only with specified data.

I have gotten this same error with 5.0.37 built manually to include SSl support using both an OpenSSL and sslya.  In my case the core dump occurs after inputting a password and occurs whether the passwords and account are real or bogus.

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".

For the record: I got the same error with 5.0.37 on Solaris 9 Sparc. 5.0.45 compiled with the same options did not coredump any more.