summaryrefslogtreecommitdiff
path: root/cmd-line-utils
diff options
context:
space:
mode:
authorunknown <holyfoot/hf@mysql.com/hfmain.(none)>2007-05-20 21:22:57 +0500
committerunknown <holyfoot/hf@mysql.com/hfmain.(none)>2007-05-20 21:22:57 +0500
commit59a7e066e3a86bb4371ce5027b4ad6b79ac91ce2 (patch)
tree02abebc14d64d25a68e4845a50e8f39f7ca0adb0 /cmd-line-utils
parent8b33c41554b1f9ac173a047f55fa0c522f28af35 (diff)
downloadmariadb-git-59a7e066e3a86bb4371ce5027b4ad6b79ac91ce2.tar.gz
bug #28361 Buffer overflow in DECIMAL code on Windows
my_decimal in some cases can contain more decimal digits than is officially supported (DECIMAL_MAX_PRECISION), so we need to prepare bigger buffer for the resulting string. mysql-test/r/type_newdecimal.result: bug #28361 Buffer overflow in DECIMAL code on Windows test result mysql-test/t/type_newdecimal.test: bug #28361 Buffer overflow in DECIMAL code on Windows test case This test case doesn't fall in most cases even without the fix Still valgrind shows the problemn sql/my_decimal.h: bug #28361 Buffer overflow in DECIMAL code on Windows DECIMAL_MAX_POSSIBLE_PRECISION introduced to be used in places, when we need to check for the number of digits technicaly possible in my_decimal. DECIMAL_MAX_STR_LENGTH fixed as it has to fit for the MAX_POSSIBLE_PRECISION
Diffstat (limited to 'cmd-line-utils')
0 files changed, 0 insertions, 0 deletions