Hi. Just my two cents. I think this might be the same as this:
https://bugs.kde.org/show_bug.cgi?id=395682 and respectively https://sourceware.org/bugzilla/show_bug.cgi?id=23357 It seems a default option for ld (-z separate-code) was changed, which makes valgrind unable to read the binaries info. This in turn (and here is where the guessing starts) may lead to valgrind not being able to apply its default suppressions!? Regards Andre On 10.07.2018 11:43, Aurelien Jarno wrote: > On 2018-07-09 13:00, Paul Gevers wrote: >> Source: glibc, unrar-free >> Version: glibc/2.27-4 >> Version: unrar-free/1:0.0.1+cvs20140707-4 >> User: [email protected] >> Usertags: breaks needs-update >> >> Dear maintainers, >> >> With a recent upload of glibc the autopkgtest of unrar-free started to >> fail in unstable and testing. I have copied the error below. >> >> Currently this regression is delaying the migration of glibc to >> testing by 13 days. Could you please investigate the situation and >> determine which package needs to fix something, and assign appropriately? > > From what I have investigated so far, valgrind returns many "Conditional > jump or move depends on uninitialised value" issues when libc6 is built > using binutils 2.30.90.20180705-1. When rebuilding libc6 2.27-4 with > binutils 2.30-22, the issue disappears. > > I don't know yet, if it's an issue in glibc, binutils or valgrind, > however I doubt it's an issue in unrar-free. > > Aurelien >
signature.asc
Description: OpenPGP digital signature
