Bug #38469 invalid memory read and/or crash with utf8 text field, stored procedure, uservar
Submitted: 30 Jul 2008 20:21 Modified: 20 Oct 2008 17:31
Reporter: Shane Bester
Status: Closed
Category:Server: SP Severity:S1 (Critical)
Version:5.0.66a, mysql-5.1.26-rc-linux-i686-glibc23, 5.1.28 OS:Any
Assigned to: Kristofer Pettersson Target Version:5.1.29,5.0+
Triage: Triaged: D1 (Critical)

File: Maximum allowed size is 500KB.
Description:
Privacy:

If the data you need to attach is more than 500KB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (example: bug-data-38469.zip), and use FTP to upload the archive to ftp://ftp.mysql.com/pub/mysql/upload/. Once you have uploaded the file, add a comment to this bug to notify us about it. Note: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it.

All entries become the exclusive editorial property of Sun Microsystems, Inc.

[30 Jul 2008 20:23] Shane Bester 
full stack1

Attachment: bug38469_full_stack_5.0.66a.txt (text/plain), 3.56 KiB.
[31 Jul 2008 10:00] Shane Bester 
under valgrind on 5.0.66a on linux there are errors. they are interrmittent though

Attachment: bug38469_valgrind_errors_and_testcase.txt (text/plain), 8.08 KiB.
[15 Sep 2008 10:07] Shane Bester 
valgrind output from 5.1.28

Attachment: bug38469.txt (text/plain), 7.50 KiB.