Commit cd347313 authored by Tor Didriksen's avatar Tor Didriksen

Bug#12856915 VALGRIND FAILURE IN FILESORT/CREATE_SORT_INDEX

Post-push fix:
Replace fun:inline_mysql_file_write with '...' since it may be optimized away.
parent e7b37d72
...@@ -880,13 +880,16 @@ ...@@ -880,13 +880,16 @@
# Note the wildcard in the (mangled) function signatures of # Note the wildcard in the (mangled) function signatures of
# write_keys() and find_all_keys(). # write_keys() and find_all_keys().
# They both return ha_rows, which is platform dependent. # They both return ha_rows, which is platform dependent.
#
# The '...' wildcards are for 'fun:inline_mysql_file_write' which *may*
# be inlined.
{ {
Bug#12856915 VALGRIND FAILURE IN FILESORT/CREATE_SORT_INDEX / one Bug#12856915 VALGRIND FAILURE IN FILESORT/CREATE_SORT_INDEX / one
Memcheck:Param Memcheck:Param
write(buf) write(buf)
obj:*/libpthread*.so obj:*/libpthread*.so
fun:my_write fun:my_write
fun:inline_mysql_file_write ...
fun:my_b_flush_io_cache fun:my_b_flush_io_cache
fun:_my_b_write fun:_my_b_write
fun:_Z*10write_keysP13st_sort_paramPPhjP11st_io_cacheS4_ fun:_Z*10write_keysP13st_sort_paramPPhjP11st_io_cacheS4_
...@@ -900,7 +903,7 @@ ...@@ -900,7 +903,7 @@
write(buf) write(buf)
obj:*/libpthread*.so obj:*/libpthread*.so
fun:my_write fun:my_write
fun:inline_mysql_file_write ...
fun:my_b_flush_io_cache fun:my_b_flush_io_cache
fun:_Z15merge_many_buffP13st_sort_paramPhP10st_buffpekPjP11st_io_cache fun:_Z15merge_many_buffP13st_sort_paramPhP10st_buffpekPjP11st_io_cache
fun:_Z8filesortP3THDP5TABLEP13st_sort_fieldjP10SQL_SELECTybPy fun:_Z8filesortP3THDP5TABLEP13st_sort_fieldjP10SQL_SELECTybPy
...@@ -912,7 +915,7 @@ ...@@ -912,7 +915,7 @@
write(buf) write(buf)
obj:*/libpthread*.so obj:*/libpthread*.so
fun:my_write fun:my_write
fun:inline_mysql_file_write ...
fun:my_b_flush_io_cache fun:my_b_flush_io_cache
fun:_Z8filesortP3THDP5TABLEP13st_sort_fieldjP10SQL_SELECTybPy fun:_Z8filesortP3THDP5TABLEP13st_sort_fieldjP10SQL_SELECTybPy
} }
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment