| Bug #43028 | Freeing pointer out of range for on restore of archive table | ||
|---|---|---|---|
| Submitted: | 19 Feb 2009 18:31 | Modified: | 1 Apr 2009 12:59 |
| Reporter: | Chuck Bell | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Backup | Severity: | S3 (Non-critical) |
| Version: | 6.0.10 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
[20 Feb 2009 7:14]
Sveta Smirnova
Thank you for the report. > How to repeat: > Run the attached test. But there is no atttached test. Please attach it.
[20 Feb 2009 13:30]
Chuck Bell
Test
Attachment: bup_part_bug2.test (application/octet-stream, text), 933 bytes.
[20 Feb 2009 13:30]
Chuck Bell
DOH! Sorry about that. File is attached.
[21 Feb 2009 8:06]
Sveta Smirnova
Thank you for the feedback. I can not repeat described behavior in my environment. On which machine do you get this error?
[23 Feb 2009 14:09]
Chuck Bell
Windows Vista Ultimate 32-bit with Visual Studio 2008 Professional.

Description: Restoring an archive table can produce an error in MTR freeing a pointer out of range on the Windows platform. main.bup_part_bug2 [ fail ] Found warnings/errors in serv er log file! Test ended at 2009-02-19 12:47:36 file_name line c:/source/bzr/mysql-6.0-bug-41642/mysql-test/var/mysqld.1/mysqld.err Error: F reeing pointer out of range at line 399, '.\ha_archive.cc' c:/source/bzr/mysql-6.0-bug-41642/mysql-test/var/mysqld.1/mysqld.err Error: F reeing pointer out of range at line 399, '.\ha_archive.cc' c:/source/bzr/mysql-6.0-bug-41642/mysql-test/var/mysqld.1/mysqld.err Error: F reeing pointer out of range at line 399, '.\ha_archive.cc' ^ Found warnings!! ok This error can be reproduced in the mysql-6.0 and mysql-6.0-backup trees. Note: The backup_engines.backup_partition test has been disabled for the archive storage engine. When this bug is fixed, that test should be reenabled. See the test for details. How to repeat: Run the attached test. Note that this error does not occur on all Windows platforms. I have not been able to trace the source. It appears that the close_tables call in the backup is the path where this error manifests. Suggested fix: Debug the calls to close_tables WRT the error produced at line 399 in ha_archive.cc.