Bug #20016 error in mgm protocal parser error message incorrect
Submitted: 23 May 2006 4:39 Modified: 19 Jun 2006 17:40
Reporter: Stewart Smith Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0.21 OS:
Assigned to: Stewart Smith CPU Architecture:Any

[23 May 2006 4:39] Stewart Smith
       * Print some info about why the parser returns NULL
              "Error in mgm protocol parser. cmd: >%s< status: %d curr: %d\n",
              cmd, (Uint32)ctx.m_status, ctx.m_currentToken);
      DBUG_PRINT("info",("ctx.status: %d, ctx.m_currentToken: %s",
                         ctx.m_status, ctx.m_currentToken));

in fprintf, last %d should be %s

How to repeat:
break mgm protocol, look at error message. see it's less useful than you wish it would be.

Suggested fix:
as above.
[23 May 2006 4:46] Bugs System
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:

[5 Jun 2006 8:36] Tomas Ulin
19 - patch approved, get it in asap
[16 Jun 2006 11:42] Stewart Smith
pushed to 5.1.12 and 5.0.23
[19 Jun 2006 17:40] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Documented bugfix in 5.0.23/5.1.12 changelogs; closed.