Bug #12528 yassl interferes with memory management

• Submitted: 11 Aug 2005 15:39
• Modified: 27 Sep 2005 10:26
• Reporter: Joerg Bruehe
• Status: Closed
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.0.11
• OS: Other (OpenBSD + others)
• Assigned to: Magnus Blåudd
• CPU Architecture: Any

[11 Aug 2005 15:39] Joerg Bruehe

Description:
Test build including "yassl" on all platforms.

Test failure:

init_connect                   [ fail ]

Errors are (from PATH/mysqltest-time) :
mysqltest in free(): error: chunk is already free
mysqltest returned unexpected code 134, it has probably crashed
(the last lines may be the most important ones)

ds9-5.0-standard.log   normal

"init_connect" failed on other platforms as well, but typically caused infinite loops in "mysqltest".
This occurred on "hammer", "ita2", and "quadita2" in "max" builds.

How to repeat:
Test suite failure.

[26 Aug 2005 13:52] Magnus Blåudd

On linux compiled with icc:
TEST                            RESULT
-------------------------------------------------------
*** glibc detected *** double free or corruption (!prev): 0x09034b00 ***
init_connect                   [ fail ]

mysqltest returned unexpected code 134, it has probably crashed

[5 Sep 2005 9:24] Magnus Blåudd

Occured on "build" in latest yaSSL build

10351: init_connect                    [ fail ]
10352: Errors are (from /build/mysqldev/build/test/mysql-standard-5.0.13-beta-yassl-linux-i686/mysql-test/var/log/mysqltest-time) :
10353: mysqltest returned unexpected code 139, it has probably crashed
10354: (the last lines may be the most important ones)
10355: 
10356: Ending Tests
10357: Shutting-down MySQL daemon
10358: 
10359: Master(s) shutdown finished
10360: Slave(s) shutdown finished
10361: Resuming Tests
10362:

[27 Sep 2005 10:26] Magnus Blåudd

This problem have been fixed by the latest changes to mysqltest and yassl