List:Commits« Previous MessageNext Message »
From:paul.dubois Date:April 20 2011 1:57am
Subject:svn commit - mysqldoc@oter02: r25943 - in trunk: . dynamic-docs/changelog
View as plain text  
Author: pd221994
Date: 2011-04-20 03:57:11 +0200 (Wed, 20 Apr 2011)
New Revision: 25943

Log:
 r47222@dhcp-adc-twvpn-1-vpnpool-10-154-15-118:  paul | 2011-04-19 12:30:32 -0500
 Document bug fixes:
 BUG 11760210 - 52596: SSL_CIPHER_LIST NOT SET OR RETURNED FOR "SHOW STATUS LIKE 'SSL_CIPHER_LIS
 BUG 11763784 - 56541: ASSERTION TABLE->DB_STAT FAILED IN SQL_BASE.CC::OPEN_TABLE() DURING I_S Q
 BUG 11765202 - 58140: DBUG_VIOLATION_HELPER::~DBUG_VIOLATION_HELPER(): ASSERTION `!_ENTERED' FA
 BUG 11765216 - 58154: UNINITIALIZED VARIABLE FORMAT IN STR_TO_DATE FUNCTION
 BUG 11766087 - 59125: VALGRIND UNINITIALISED VALUE WARNING IN ULL2DEC, LONGLONG2DECIMAL
 BUG 11766094 - 59132: MIN() AND MAX() REMOVE UNSIGNEDNESS
 BUG 11766112 - 59151: UNINITIALIZED VALUES IN EXTRACT_DATE_TIME WITH STR_TO_DATE(SPACE(..) ...
 BUG 11766124 - 59164: VALGRIND: UNINITIALIZED VALUE IN NUMBER_TO_DATETIME
 BUG 11766126 - 59166: ANOTHER DATETIME VALGRIND UNINITIALIZED WARNING
 BUG 11766424 - 59527: DECIMAL_BIN_SIZE: ASSERTION `SCALE >= 0 && PRECISION > 0 && SCALE <= PRE
 BUG 11792200 - DIVIDING LARGE NUMBERS CAUSES STACK CORRUPTIONS
 BUG 11849231 - ZLIB INFLATEINIT INVOKED WITHOUT INITIALIZING ALL MEMORY


Modified:
   svk:merge
   trunk/dynamic-docs/changelog/mysqld-2.xml

Property changes on: trunk
___________________________________________________________________

Modified: svk:merge
===================================================================


Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 1277 bytes


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-20 01:57:05 UTC (rev 25942)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-04-20 01:57:11 UTC (rev 25943)
Changed blocks: 1, Lines Added: 335, Lines Deleted: 0; 6529 bytes

@@ -44070,4 +44070,339 @@
 
   </logentry>
 
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="PROCEDURE ANALYSE()"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="58140"/>
+      <fixes bugid="11765202"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.11"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        The code for <literal>PROCEDURE ANALYSE()</literal> had a
+        missing <literal>DBUG_RETURN</literal> statement, which could
+        cause a server crash in debug builds.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="Ssl_cipher_list"/>
+      <manual type="SHOW STATUS"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="52596"/>
+      <fixes bugid="11760210"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.11"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        For a client connected using SSL, the
+        <literal role="statvar">Ssl_cipher_list</literal> status
+        variable was empty and did not show the possible cipher types.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="11792200"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.5.11"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Division of large numbers could cause stack corruption.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="valgrind"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="59164"/>
+      <fixes bugid="11766124"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In <literal>Item::get_date</literal>, a Valgrind warning for a
+        missing <literal>NULL</literal> value check was corrected.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="valgrind"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="59166"/>
+      <fixes bugid="11766126"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In <literal>Item_func_month::val_str()</literal>, a Valgrind
+        warning for a too-late <literal>NULL</literal> value check was
+        corrected.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="valgrind"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="59125"/>
+      <fixes bugid="11766087"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In <literal>Item_func::val_decimal</literal>, a Valgrind warning
+        for a missing <literal>NULL</literal> value check was corrected.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="valgrind"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="58154"/>
+      <fixes bugid="11765216"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In <literal>Item_func_str_to_date::val_str</literal>, a Valgrind
+        warning for an uninitialized variable was corrected.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="valgrind"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="59151"/>
+      <fixes bugid="11766112"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In <literal>extract_date_time()</literal>, a Valgrind warning
+        for a missing end-of-string check was corrected.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="zlib"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="11849231"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal role="se">InnoDB</literal> invoked some
+        <literal>zlib</literal> functions without proper initialization.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="59527"/>
+      <fixes bugid="11766424"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A missing variable initialization for
+        <literal>Item_func_set_user_var</literal> objects could cause an
+        assertion to be raised.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="MIN()"/>
+      <manual type="MAX()"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="59132"/>
+      <fixes bugid="11766094"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In string context, the <literal role="func">MIN()</literal> and
+        <literal role="func">MAX()</literal> functions did not take into
+        account the unsignedness of a <literal>BIGINT UNSIGNED</literal>
+        argument.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <manual type="locking"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="56541"/>
+      <fixes bugid="11763784"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.57"/>
+      <version ver="5.5.12"/>
+      <version ver="5.6.3"/>
+    </versions>
+
+    <message>
+
+      <para>
+        An assertion could be raised if a statement that required a name
+        lock on a table (for example, <literal role="stmt">DROP
+        TRIGGER</literal>) executed concurrently with an
+        <literal>INFORMATION_SCHEMA</literal> query that also used the
+        table.
+      </para>
+
+    </message>
+
+  </logentry>
+
 </changelog>


Thread
svn commit - mysqldoc@oter02: r25943 - in trunk: . dynamic-docs/changelogpaul.dubois20 Apr