Bus error when using mysqldump

Message

Biffen · Post by **Biffen** » Tue Dec 05, 2006 7:11 am

Hi,

I have problems after upgraded mysql from 4.1.21 to 5.0.26. I got bus error when using mysqldump, all works fine when using phpmyadmin dumping databases. Any tip whats wrong?

Netra X1 512 meg ram:
linux-2.4.32-sparc-r6

Greets,

Biffen

Ferris · Post by **Ferris** » Tue Dec 05, 2006 12:49 pm

A bus error usually results from a data alignment problem. I can duplicate the problem, so I believe that the mysqldump program itself is creating misaligned data. There is nothing you can do yourself (unless you want to fix mysqldump), but you should file a bug report against mysql (which is where mysqldump comes from).

In other words, you are not doing anything wrong; mysqldump is. Please file a bug report at http://bugs.gentoo.org (with architecture = sparc) against dev-db/mysql-5.0.26.

(By the way, my experiences with that upgrade suggest that mysql-4.1.21 databases should work with mysql-5.0.26 without conversion. Are you seeing something different?)

Regards,
Ferris

Biffen · Post by **Biffen** » Thu Dec 07, 2006 8:46 am

Ferris wrote:A bus error usually results from a data alignment problem. I can duplicate the problem, so I believe that the mysqldump program itself is creating misaligned data. There is nothing you can do yourself (unless you want to fix mysqldump), but you should file a bug report against mysql (which is where mysqldump comes from).

In other words, you are not doing anything wrong; mysqldump is. Please file a bug report at http://bugs.gentoo.org (with architecture = sparc) against dev-db/mysql-5.0.26.

(By the way, my experiences with that upgrade suggest that mysql-4.1.21 databases should work with mysql-5.0.26 without conversion. Are you seeing something different?)

Regards,
Ferris

Ok, sending a bug report.

I used the http://www.gentoo.org/doc/en/mysql-upgrading.xml part 1 for upgrade.

Biffen · Post by **Biffen** » Thu Dec 07, 2006 12:36 pm

Intresting... got this when I made a bug report:

"reopen once you've posted all the relevant information here."

How could I know whats relevant? =P

Biffen · Post by **Biffen** » Thu Dec 07, 2006 12:48 pm

bug report here:

http://bugs.gentoo.org/show_bug.cgi?id=157408

Biffen · Post by **Biffen** » Tue Dec 12, 2006 12:46 pm

Not fixed in the latest mysql-5.0.30.ebuild, will go back to mysql-4.1.21.

Ferris · Post by **Ferris** » Tue Dec 12, 2006 1:23 pm

As noted on your bug report, we know what and where the problem is, and the MySQL upstream developers have been notified. It's up to them to fix it, I think, because the failure comes from widening a pointer '(char*) arg' to reference it as '*(uint*) arg' --- something which is generally prohibited on sparc because of sparc's data alignment requirements. A patch is easy, but whether or not it is a good fix depends on just what MySQL has arg pointing to in the first place.

Biffen · Post by **Biffen** » Thu Dec 14, 2006 7:06 am

Ferris wrote:As noted on your bug report, we know what and where the problem is, and the MySQL upstream developers have been notified. It's up to them to fix it, I think, because the failure comes from widening a pointer '(char*) arg' to reference it as '*(uint*) arg' --- something which is generally prohibited on sparc because of sparc's data alignment requirements. A patch is easy, but whether or not it is a good fix depends on just what MySQL has arg pointing to in the first place.

Yes, time will tell. No problem for me, using 4.1.21 for now.