Bug #24896 mysql_upgrade core dumps on RHEL3 using 5.0.30 commerical binaries

Description:
mysql_upgrade seg faults (core dumps) when I run it.  This happened on an upgrade from community binaries (5.0.27) to commericial binaries (5.0.30).  I uninstalled the RPMS, and re-installed version 5.0.30, and found the same behavior

OS: Red Hat Enterprise Linux ES release 3 (Taroon Update 4)
RPMS:
MySQL-client-enterprise-5.0.30-0.rhel3.i386
(server,shared, and devel also installed, same version)

I verified it was "not my system" by installing MySQL-<client,server,etc>-enterprise-5.0.28-0.rhel3.i386 and got the expected behavior.

How to repeat:
install version 5.0.30 of the commerical (OEM) binaries
[root]# mysql_upgrade --basedir=/usr -p

Suggested fix:
I didn't even look at the cores, i'm assuming they're stripped and don't have debug symbols.  So, I just backed off to versin 5.0.28

Thank you for a bug report. Verified just as described.

Manually set to patch pending.

http://lists.mysql.com/commits/16634

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/16833

ChangeSet@1.2328, 2006-12-12 15:47:02+01:00, df@kahlann.erinye.com +1 -0
  BUG#24896 magnus' suggestion

Note that the same bug exists in 5.1.14 and I can confirm that patch attached to this issue fixes the problem in that version, too.

This error can also appear as "Bus Error" on Mac OSX.

The problem again only occurs when the -p or --password option is specified.

Marked 18156 as a partial duplicate of this bug.

Bug fix is in 5.0.32 and will be in 5.1.15.

Noted in 5.0.32, 5.1.15 changelogs.

mysql_upgrade failed if the --password (or -p) option was given.