MySQL Bugs: #44358: valgrind errors with decode() function

Bug #44358	valgrind errors with decode() function
Submitted:	20 Apr 2009 5:49	Modified:	12 May 2009 2:47
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S1 (Critical)
Version:	5.1.32, 5.1.35	OS:	Linux
Assigned to:	Sergei Glukhov	CPU Architecture:	Any
Tags:	decode, GIGO, valgrind

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

a more potent testcase, that causes invalid reads of memory (hence, can crash)

Attachment: bug44358_new_testcase.sql (application/unknown, text), 6.32 KiB.

the new testcase valgrind outputs from 5.1.32

Attachment: bug44358_new_valgrind_outputs.txt (text/plain), 16.90 KiB.