Bug #42188 crash and/or memory corruption with user variables in trigger
Submitted: 18 Jan 2009 21:39 Modified: 11 Feb 2009 3:39
Reporter: Frederic Steinfels Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Stored Routines Severity:S1 (Critical)
Version:5.1.29, 5.1.30, 5.1.31, 6.0.8, 6.0.10 OS:Any
Assigned to: Gleb Shchepa CPU Architecture:Any
Tags: corruption, crash, mysql_change_user, regression, stored procedure, trigger

File: Maximum allowed size is 3MB.

If the data you need to attach is more than 3MB, 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 (recommended filename: mysql-bug-data-42188.zip) and upload one to sftp.oracle.com. A free Oracle Web (SSO) account (the one you use to login bugs.mysql.com) and a client that supports SFTP are required in order to access the SFTP server.

To upload the file to sftp.oracle.com:

  1. Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/.
  2. Log in with your newly created Oracle Web account (email address) and password.
  3. Upload the archive to /support/incoming.
  4. Once you have uploaded the file, add a comment to this bug to notify us about it.
Example: sftp -oPort=2021 -oUser=email sftp.oracle.com:/support/incoming

Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed.

[19 Jan 2009 18:07] Shane Bester
testcase. run against mysqld-debug or mysqld under valgrind if crashes don't happen soon

Attachment: bug42188.c (text/plain), 6.96 KiB.