Bug #51625 ErrorReporter::formatMessage truncates a long message
Submitted: 2 Mar 2010 1:01 Modified: 29 Apr 2013 13:57
Reporter: jack andrews Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-7.0 OS:Any
Assigned to: Assigned Account CPU Architecture:Any

[2 Mar 2010 1:01] jack andrews
Description:
in Bug #47120  	ErrorReporter::formatMessage overruns the buffer

magnus wrote:

Patch fixes the problem ok but it shows another small flaw in our
ErrorReporter. When crashing with a long "problemData" string the other
interesting fields like "Error object:", "Version: " and "Trace: " are
not written. See below. Please write a follow up bug for fixing that.
Suggested solution is to either truncate the string to a more sensible
length or maybe we should abandon the fixed size length of these error
messages(which we have implemented in order to avoid filling disks with
logs) and instead go for a max length of the error log.

How to repeat:
Bug #47120  	ErrorReporter::formatMessage overruns the buffer

Suggested fix:
make log message bigger
[2 Mar 2010 1:26] 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:

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

3414 Jack Andrews	2010-03-02
      Bug #51625  	ErrorReporter::formatMessage truncates a long message
      
       . increase the max message size
[4 Mar 2010 3:17] 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:

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

3414 Jack Andrews	2010-03-04
      Bug #51625        ErrorReporter::formatMessage truncates a long message
        . move important messages to top of formatMessage in case of truncation
[4 Mar 2010 11:03] jack andrews
utc
[29 Apr 2013 13:57] Magnus BlÄudd
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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html