Bug 23397

Summary: valgrind generates question marks errors for ./fc-solve with the new "glibc"s
Product: Mageia Reporter: Shlomi Fish <shlomif>
Component: RPM PackagesAssignee: Base system maintainers <basesystem>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11, thierry.vignaud, tmb
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: glibc-2.28-0.5.mga7, valgrind CVE:
Status comment:

Description Shlomi Fish 2018-08-06 17:59:41 CEST 
Description of problem:

valgrind ./fc-solve 24.board has started generating errors on cauldron (try bm -l -b ing the "freecell-solver" package. The tests with valgrind run fine on Travis-CI ubuntu 14.04.

=============================

shlomif[fcs]:$trunk/fc-solve/B$ valgrind --vgdb=full --vgdb-error=1 ./fc-solve 24.board                                                                                                                                                     
==11252== Memcheck, a memory error detector
==11252== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==11252== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==11252== Command: ./fc-solve 24.board
==11252==
==11252==
==11252== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==11252==   /path/to/gdb ./fc-solve
==11252== and then give GDB the following command
==11252==   target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=11252
==11252== --pid is optional if only one valgrind process is running
==11252==
-=-=-=-=-=-=-=-=-=-=-=-

==11252== Conditional jump or move depends on uninitialised value(s)
==11252==    at 0x4AB7F1E: ??? (in /usr/lib64/libc-2.28.so)
==11252==    by 0x202020202020201F: ???
==11252==    by 0x202020202020201F: ???
==11252==    by 0x20302D4320302D47: ???
==11252==    by 0xA302D5320302D43: ???
==11252==    by 0x202D2D2D202D2D2C: ???
==11252==    by 0x202D2D2D202D2D2C: ???
==11252==    by 0x20202D2D200A0A09: ???
==11252==    by 0x20202D2D20202D2C: ???
==11252==    by 0x20202D2D20202D2C: ???
==11252==    by 0x20202D2D20202D2C: ???
==11252==    by 0x204334200A202D2C: ???
==11252==
==11252== (action on error) vgdb me ...

==========================

shlomif[fcs]:$trunk/fc-solve/B$ gdb ./fc-solve
GNU gdb (GDB) 8.1-2.mga7 (Mageia release 7)
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-mageia-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./fc-solve...done.
(gdb) target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=11252
Remote debugging using | /usr/lib64/valgrind/../../bin/vgdb --pid=11252
relaying data between gdb and process 11252
warning: remote target does not support file transfer, attempting to access files from local filesystem.
Reading symbols from /usr/lib64/valgrind/vgpreload_core-amd64-linux.so...done.
Reading symbols from /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so...done.
Reading symbols from /home/shlomif/progs/freecell/git/fc-solve/fc-solve/B/libfreecell-solver.so.0...done.
Reading symbols from /lib64/libm.so.6...Reading symbols from /usr/lib/debug/lib64/libm-2.28.so-2.28-0.5.mga7.x86_64.debug...done.                                                                                                           
done.
Reading symbols from /lib64/libc.so.6...Reading symbols from /usr/lib/debug/lib64/libc-2.28.so-2.28-0.5.mga7.x86_64.debug...done.                                                                                                           
done.
Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib64/ld-2.28.so-2.28-0.5.mga7.x86_64.debug...done.                                                                                                  
done.
__strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:228
228             jne     L(exit64)
(gdb) bt
#0  __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:228
#1  0x0000000004a8fba5 in fputs () at iofputs.c:33
#2  0x0000000000402530 in fc_solve_output_result_to_file (output_fh=0x4be0760 <_IO_2_1_stdout_>, instance=0x4029260, ret=0, dc_ptr=0x407380 <display_context>)                                                                              
    at /home/shlomif/progs/freecell/git/fc-solve/fc-solve/source/output_to_file.h:82
#3  0x0000000000403542 in main (argc=2, argv=0x1ffefff098) at /home/shlomif/progs/freecell/git/fc-solve/fc-solve/source/cl_callback.h:382                                                                                                   
(gdb) frame 2
#2  0x0000000000402530 in fc_solve_output_result_to_file (output_fh=0x4be0760 <_IO_2_1_stdout_>, instance=0x4029260, ret=0, dc_ptr=0x407380 <display_context>)                                                                              
    at /home/shlomif/progs/freecell/git/fc-solve/fc-solve/source/output_to_file.h:82
82                  fputs(state_as_string, output_fh);
(gdb) p state_as_string
$1 = ' ' <repeats 24 times>, "H-0 C-0 D-0 S-0\n--- --- --- --- \n\n\n --  --  --  --  --  --  --  -- \n 4C  5H  QC  5D  2D  7H  AH  7S \n 2C  QH  9S  2S  KD  JS  5S  6C \n 9C  3C  6H  JC 10H  KH  6S  7D \n 8C  AC  "...                  
(gdb)
Marja Van Waes 2018-08-07 08:03:34 CEST

CC: (none) => marja11, tmb
Assignee: bugsquad => basesystem

Comment 1 Shlomi Fish 2018-08-07 09:41:58 CEST 
I should note that I was able to work around the problem by building valgrind from its git repository's master HEAD and putting it in the $PATH .
Comment 2 Marja Van Waes 2018-08-07 09:47:43 CEST 
(In reply to Shlomi Fish from comment #1)
> I should note that I was able to work around the problem by building
> valgrind from its git repository's master HEAD and putting it in the $PATH .

CC'ing Thierry

CC: (none) => thierry.vignaud
Source RPM: glibc-2.28-0.5.mga7.src.rpm => glibc-2.28-0.5.mga7, valgrind

Comment 3 Shlomi Fish 2019-02-19 11:47:04 CET 
It is fixed now.

Resolution: (none) => FIXED
Status: NEW => RESOLVED