[MDEV-11910] Valgrind warnings/erros with __strcmp_ssse3 in the libc library Created: 2017-01-25  Updated: 2017-02-14  Resolved: 2017-02-14

Status: Closed
Project: MariaDB Server
Component/s: Configuration
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Varun Gupta (Inactive) Assignee: Jani Tolonen
Resolution: Fixed Votes: 0
Labels: None


 Comments   
Comment by Varun Gupta (Inactive) [ 2017-01-25 ] 

CALL mtr.add_suppression("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT");
 
call mtr.add_suppression("Table 't1' is marked as crashed and should be repaired");
 
CREATE TABLE t2 (
 
auto int,
 
fld1 int(6) unsigned zerofill DEFAULT '000000' NOT NULL,
 
companynr tinyint(2) unsigned zerofill DEFAULT '00' NOT NULL,
 
fld3 char(30) DEFAULT '' NOT NULL,
 
fld4 char(35) DEFAULT '' NOT NULL,
 
fld5 char(35) DEFAULT '' NOT NULL,
 
fld6 char(4) DEFAULT '' NOT NULL
 
) ENGINE=archive;
 
INSERT INTO t2 VALUES (1,000001,00,'Omaha','teethe','neat','');
 
drop table t2;

Comment by Varun Gupta (Inactive) [ 2017-01-25 ]

First Vagrind warning for the above testcase

==26056== Invalid read of size 8
==26056== at 0x6B6A3EE: __strcmp_ssse3 (in /lib64/libc-2.18.so)
==26056== by 0xF06875: array_append_string_unique (mf_arr_appstr.c:44)
==26056== by 0xEEF22C: add_directory (my_default.c:1121)
==26056== by 0xEEF324: init_default_directories (my_default.c:1236)
==26056== by 0xEED75E: my_load_defaults (my_default.c:523)
==26056== by 0xEED6B4: load_defaults (my_default.c:466)
==26056== by 0x550600: mysqld_main(int, char**) (mysqld.cc:5531)
==26056== by 0x545EA7: main (main.cc:25)

Comment by Daniel Black [ 2017-01-26 ]

what valgrind version are you using? This could be valgrind bug 311407 fixed in valgrind 3.9.0 - http://www.valgrind.org/docs/manual/dist.news.html

Comment by Sergei Petrunia [ 2017-01-27 ]

danblack, checking.. the machine has valgrind-3.11.0, so it's not that bug (although could be still a similar issue)

Comment by Sergei Petrunia [ 2017-01-27 ]

... However, if I upgrade to valgrind-3.12.0, the error goes away! At least for mysql-test-run t/alias.test : I get plenty of errors with valgrind 3.11.0, but the test passes with valgrind 3.12.0

Comment by Elena Stepanova [ 2017-01-27 ]

jani,

Could you please upgrade valgrind to 3.12.x?
It's rather urgent.

Comment by Jani Tolonen [ 2017-02-14 ]

Installed 3.12.0 under /usr/local/bin. No RPM available with higher version number than 3.11.0 for openSuSE at the moment.

Comment by Daniel Black [ 2017-02-14 ]

FYI there are some here, either directly or additional repository

http://software.opensuse.org/download.html?project=devel%3Atools&package=valgrind

If you come into this kind of error again, the valgrind folks are reasonably quick to fix this kind of thing, just need a binary encoding at a point (or the entire library). The rest can be decoded via documentation and implemented.

Generated at Thu Feb 08 07:53:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.