[MDEV-3143] LP:473914 - mysql_client_test fail on windows x64 Created: 2009-11-04  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Oleksandr Byelkin Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug473914.xml    

 Description   

The test fails with attempt to access memory 0xcccccccccccccccc in output_l called from fprintf, TERMINATE, mysql_print_status() (519).

 Comments   
Comment by Oleksandr Byelkin [ 2009-11-04 ]

Re: mysql_client_test fail on windows x64
The memory which is corrupted was allocated between two ha_initialize_handlerton() calls, so probably it is also ha_initialize_handlerton() call:
hton= (handlerton *)my_malloc(sizeof(handlerton),
MYF(MY_WME | MY_ZEROFILL));
So the bug can be related to archive engine failures (also casued by memorry overrun)

Comment by Oleksandr Byelkin [ 2009-11-05 ]

Re: mysql_client_test fail on windows x64
but can be reproduced by just COM_DEBUG (mysqladmin debug).

Comment by Sergei Petrunia [ 2009-11-30 ]

Re: mysql_client_test fail on windows x64
The problem is not repeatable on 32-bit Windows.

Comment by Henrik Ingo (Inactive) [ 2009-12-22 ]

Re: mysql_client_test fail on windows x64
Btw: We can release 5.1 final without Win64 support, so strictly speaking the 5.1 tag can be removed for this bug.

Comment by Hakan Küçükyılmaz (Inactive) [ 2009-12-22 ]

Re: mysql_client_test fail on windows x64
Just removed the "5.1" tag.

Comment by Rasmus Johansson (Inactive) [ 2011-12-13 ]

Launchpad bug id: 473914

Generated at Thu Feb 08 06:46:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.