Bug #10188 type_timestamp.test: valgrind warning: Source and destination overlap in memcpy
Submitted: 26 Apr 2005 20:38 Modified: 23 May 2005 14:50
Reporter: Sergey Petrunya Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0-bk OS:
Assigned to: Michael Widenius CPU Architecture:Any

[26 Apr 2005 20:38] Sergey Petrunya 
Description:
I've got this while running type_timestamp.test with valgrind: 
==23274== Source and destination overlap in memcpy(0x1D4728E9, 0x1D4728E9, 4)
==23274==    at 0x1B90591E: memcpy (mac_replace_strmem.c:113)
==23274==    by 0x82F8F74: field_conv(Field*, Field*) (field_conv.cc:608)
==23274==    by 0x81517DE: Item_field::save_in_field(Field*, bool) (item.cc:3215)
==23274==    by 0x8226B07: fill_record(THD*, List<Item>&, List<Item>&, bool) (sql_base.cc:3822)
==23274==    by 0x825DDB2: mysql_update(THD*, st_table_list*, List<Item>&, List<Item>&, Item*, unsigned, st_order*, unsigned long long, enum_duplicates, bool) (sql_update.cc:401)
==23274==    by 0x81FBF68: mysql_execute_command(THD*) (sql_parse.cc:3109)
==23274==    by 0x82021D0: mysql_parse(THD*, char*, unsigned) (sql_parse.cc:5178)
==23274==    by 0x81F7F46: dispatch_command(enum_server_command, THD*, char*, unsigned) (sql_parse.cc:1651)
==23274==    by 0x81F77DC: do_command(THD*) (sql_parse.cc:1457)
==23274==    by 0x81F696C: handle_one_connection (sql_parse.cc:1114)
==23274==    by 0x1BA87BBA: thread_wrapper (vg_libpthread.c:867)
==23274==    by 0xB000F64F: do__quit (vg_scheduler.c:1872)

Server built with compile-pentium-valgrind-max, last cset:
ChangeSet@1.1886, 2005-04-26 02:24:37+04:00, sergefp@mysql.com
  Merge 5.0-build -> 5.0 : keep NDB_VERSION_BUILD=6

How to repeat:
Run type_timestamp.test with valgrind.
[23 May 2005 14:50] Michael Widenius 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html