Valgrind Problems for Innodb

Bug #358518 reported by Brian Aker
2
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
High
Brian Aker
7.0
Fix Released
High
Brian Aker

Bug Description

MySQL reference for bug -> http://bugs.mysql.com/bug.php?id=44186

We are seeing a lot of messages like this in the current plugin:
==23993== Conditional jump or move depends on uninitialised value(s)
==23993== at 0x66BB80: rw_lock_x_lock_func (sync0rw.ic:292)
==23993== by 0x6188C2: log_group_checkpoint (log0log.c:1782)
==23993== by 0x61A1EF: log_checkpoint (log0log.c:1890)
==23993== by 0x61A4C6: log_fsp_current_free_limit_set_and_checkpoint (log0log.c:173)
==23993== by 0x5FCFF1: fsp_fill_free_list (fsp0fsp.c:1378)
==23993== by 0x6002BE: fsp_header_init (fsp0fsp.c:994)
==23993== by 0x669AB2: innobase_start_or_create_for_mysql (srv0start.c:1462)
==23993== by 0x5BBD39: _ZL13innobase_initPv (ha_innodb.cc:2082)
==23993== by 0x56C812: storage_engine_initializer(st_plugin_int*)
(storage_engine.cc:205)
==23993== by 0x5078F8: _ZL17plugin_initializeP13st_plugin_int (sql_plugin.cc:599)
==23993== by 0x5094D7: plugin_init(int*, char**, int) (sql_plugin.cc:708)
==23993== by 0x4168B0: main (drizzled.cc:1562)

This can be seen by just starting the Drizzle daemon binary up in valgrind and then shutting it down.

Changed in drizzle:
assignee: nobody → Brian Aker (brianaker)
importance: Undecided → High
milestone: none → aloha
status: New → Confirmed
Revision history for this message
Brian Aker (brianaker) wrote : Re: [Bug 358518] Re: Valgrind Problems for Innodb

Hi!

I believe there is a similar bug on this for MySQL right now. This bug
is in the Innodb plugin.

Cheers,
 -Brian

On May 17, 2009, at 11:55 AM, Lee Bieber wrote:

> ** Changed in: drizzle
> Importance: Undecided => High
>
> ** Changed in: drizzle
> Status: New => Confirmed
>
> ** Changed in: drizzle
> Milestone: None => aloha
>
> ** Changed in: drizzle
> Assignee: (unassigned) => Brian Aker (brianaker)
>
> --
> Valgrind Problems for Innodb
> https://bugs.launchpad.net/bugs/358518
> You received this bug notification because you are a member of
> Drizzle-
> developers, which is subscribed to Drizzle.
>
> Status in A Lightweight SQL Database for Cloud and Web: Confirmed
>
> Bug description:
> MySQL reference for bug -> http://bugs.mysql.com/bug.php?id=44186
>
> We are seeing a lot of messages like this in the current plugin:
> ==23993== Conditional jump or move depends on uninitialised value(s)
> ==23993== at 0x66BB80: rw_lock_x_lock_func (sync0rw.ic:292)
> ==23993== by 0x6188C2: log_group_checkpoint (log0log.c:1782)
> ==23993== by 0x61A1EF: log_checkpoint (log0log.c:1890)
> ==23993== by 0x61A4C6:
> log_fsp_current_free_limit_set_and_checkpoint (log0log.c:173)
> ==23993== by 0x5FCFF1: fsp_fill_free_list (fsp0fsp.c:1378)
> ==23993== by 0x6002BE: fsp_header_init (fsp0fsp.c:994)
> ==23993== by 0x669AB2: innobase_start_or_create_for_mysql
> (srv0start.c:1462)
> ==23993== by 0x5BBD39: _ZL13innobase_initPv (ha_innodb.cc:2082)
> ==23993== by 0x56C812: storage_engine_initializer(st_plugin_int*)
> (storage_engine.cc:205)
> ==23993== by 0x5078F8: _ZL17plugin_initializeP13st_plugin_int
> (sql_plugin.cc:599)
> ==23993== by 0x5094D7: plugin_init(int*, char**, int)
> (sql_plugin.cc:708)
> ==23993== by 0x4168B0: main (drizzled.cc:1562)
>
> This can be seen by just starting the Drizzle daemon binary up in
> valgrind and then shutting it down.

--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.

Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :

moving out of aloha, since this is an issue in innodb plugin

Changed in drizzle:
milestone: aloha → none
Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

I can't reproduce this in latest truck, is it still valid?

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

marked as fix released as cannot be reproduced

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.