| Bug #59166 | another datetime valgrind uninitialized warning | ||
|---|---|---|---|
| Submitted: | 25 Dec 2010 6:52 | Modified: | 19 Apr 2011 17:15 | 
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: DML | Severity: | S3 (Non-critical) | 
| Version: | 5.1.55,5.5.9,5.6.1,5.6.2 | OS: | Any | 
| Assigned to: | CPU Architecture: | Any | |
   [25 Dec 2010 6:52]
   Shane Bester        
  
 
   [25 Dec 2010 7:31]
   Sveta Smirnova        
  Sorry, mixed 2 bug reports. Ignore earlier comments. Verified as described.
   [4 Jan 2011 8:10]
   MySQL Verification Team        
  another testcase:
do mpointfromwkb(month(from_days(date_add(('2.2250738585072014E-308'),interval ('1') SECOND_MICROSECOND))));
It would appear datetime functions in general don't initialize things properly.
related: bug #59270 and bug #59164
 
   [3 Feb 2011 8:42]
   MySQL Verification Team        
  to the person who fixes this: please import this sql file (using --force or source <file>) and make sure no valgrind warnings!!
Attachment: bug59166_extended_global_variables_valgrind_test.txt (text/plain), 18.42 KiB.
   [19 Apr 2011 17:15]
   Paul DuBois        
  Noted in 5.1.57, 5.5.12, 5.6.3 changelogs. In Item_func_month::val_str(), a Valgrind warning for a too-late NULL value check was corrected. CHANGESET - http://lists.mysql.com/commits/134204

