[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Paul Howarth changed: What|Removed |Added CC||m...@fedoraproject.org --- Comment #1 from Paul Howarth --- perl-Test-Valgrind also fails to build on ppc64, with the same issues: -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Paul Howarth changed: What|Removed |Added Status|NEW |ASSIGNED Component|perl-Test-LeakTrace |perl-Test-Valgrind --- Comment #2 from Paul Howarth --- perl-Test-Valgrind also fails to build on ppc64, with the same issues: https://koji.fedoraproject.org/koji/taskinfo?taskID=20494071 https://kojipkgs.fedoraproject.org//work/tasks/4075/20494075/build.log Mark, any thoughts on how to proceed with this? -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 --- Comment #3 from Mark Wielaard --- It would be good to run the testcase by hand under valgrind with glibc-debuginfo installed so we get precise source code lines in the backtrace and using valgrind --track-origins=yes to see where exactly the issue comes from. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 --- Comment #4 from Paul Howarth --- (In reply to Mark Wielaard from comment #3) > It would be good to run the testcase by hand under valgrind with > glibc-debuginfo installed so we get precise source code lines in the > backtrace and using valgrind --track-origins=yes to see where exactly the > issue comes from. Here we go: $ make test "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- Valgrind.bs blib/arch/auto/Test/Valgrind/Valgrind.bs 644 PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'bl ib/arch')" t/*.t # Testing Test::Valgrind 1.19, Perl 5.026000, /usr/bin/perl t/00-load.t ... ok # Using valgrind 3.13.0 located at /builddir/build/BUILD/Test-Valgrind-1.19/bin/valgrind # Generating suppressions... # Suppressions for this perl stored in /builddir/.perl/Test-Valgrind/suppressions/1.19/memcheck-3.13.0-248e36fee3eae24de9070610cdef29ec.supp # Using suppressions from /builddir/.perl/Test-Valgrind/suppressions/1.19/memcheck-3.13.0-248e36fee3eae24de9070610cdef29ec.supp # 1..1 # not ok 1 - dummy test in the child, should not interfere with the actual TAP stream # # # Failed test 'dummy test in the child, should not interfere with the actual TAP stream' # # at t/10-good.t line 30. # # Looks like you failed 1 test of 1. # Conditional jump or move depends on uninitialised value(s) # __dcigettext (/usr/lib64/power8/libc-2.25.90.so) [dcigettext.c:701] # dcgettext (/usr/lib64/power8/libc-2.25.90.so) [dcgettext.c:47] # strerror_r (/usr/lib64/power8/libc-2.25.90.so) [_strerror.c:71] # Perl_my_strerror (/usr/lib64/libperl.so.5.26.0) [locale.c:2597] # Perl_magic_get (/usr/lib64/libperl.so.5.26.0) [mg.c:925] # Perl_mg_get (/usr/lib64/libperl.so.5.26.0) [mg.c:201] # Perl_sv_setsv_flags (/usr/lib64/libperl.so.5.26.0) [sv.c:4461] # Perl_pp_sassign (/usr/lib64/libperl.so.5.26.0) [pp_hot.c:226] # Perl_runops_standard (/usr/lib64/libperl.so.5.26.0) [run.c:41] # Perl_call_sv (/usr/lib64/libperl.so.5.26.0) [perl.c:2848] # Perl_call_list (/usr/lib64/libperl.so.5.26.0) [perl.c:5016] # perl_destruct (/usr/lib64/libperl.so.5.26.0) [perl.c:610] # main (/usr/bin/perl) [perlmain.c:134] # Uninitialised value was created by a stack allocation # __dcigettext (/usr/lib64/power8/libc-2.25.90.so) [dcigettext.c:490] # Conditional jump or move depends on uninitialised value(s) # __dcigettext (/usr/lib64/power8/libc-2.25.90.so) [dcigettext.c:701] # dcgettext (/usr/lib64/power8/libc-2.25.90.so) [dcgettext.c:47] # strerror_r (/usr/lib64/power8/libc-2.25.90.so) [_strerror.c:71] # Perl_my_strerror (/usr/lib64/libperl.so.5.26.0) [locale.c:2597] # Perl_magic_get (/usr/lib64/libperl.so.5.26.0) [mg.c:925] # Perl_mg_get (/usr/lib64/libperl.so.5.26.0) [mg.c:201] # Perl_sv_setsv_flags (/usr/lib64/libperl.so.5.26.0) [sv.c:4461] # Perl_pp_sassign (/usr/lib64/libperl.so.5.26.0) [pp_hot.c:226] # Perl_runops_standard (/usr/lib64/libperl.so.5.26.0) [run.c:41] # Perl_call_sv (/usr/lib64/libperl.so.5.26.0) [perl.c:2848] # Perl_call_list (/usr/lib64/libperl.so.5.26.0) [perl.c:5016] # perl_destruct (/usr/lib64/libperl.so.5.26.0) [perl.c:610] # main (/usr/bin/perl) [perlmain.c:134] # Uninitialised value was created by a stack allocation # __dcigettext (/usr/lib64/power8/libc-2.25.90.so) [dcigettext.c:490] # Failed test 'UninitCondition' # at /builddir/build/BUILD/Test-Valgrind-1.19/blib/lib/Test/Valgrind/Session.pm line 598. # got: 2 # expected: 0 # Looks like your test exited with 1 just after 15. t/10-good.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/15 subtests # Using valgrind 3.13.0 located at /builddir/build/BUILD/Test-Valgrind-1.19/bin/valgrind # Using suppressions from /builddir/.perl/Test-Valgrind/suppressions/1.19/memcheck-3.13.0-248e36fee3eae24de9070610cdef29ec.supp # dummy run-time exception, should not cause the test to fail at t/12-good-run-exception.t line 20. # Conditional jump or move depends on uninitialised value(s) # __dcigettext (/usr/lib64/power8/libc-2.25.90.so) [dcigettext.c:701] # dcgettext (/usr/lib64/power8/libc-2.25.90.so) [dcgettext.c:47] # strerror_r (/usr/lib64/power8/libc-2.25.90.so) [_strerror.c:71] # Perl_my_strerror (/usr/lib64/libperl.so.5.26.0) [locale.c:2597] # Perl_magic_get (/usr/lib64/libperl.so.5.26.0) [mg.c:925] # Perl_mg_get (/usr/lib64/libperl.so.5.26.0) [mg.c:201] # Perl_sv_setsv_flags (/usr/lib64/libperl.so.5.26.0) [sv.c:4461] # Perl_pp_sassign (/usr/lib64/libperl.so.5.26.0) [pp_hot.c:226] # Perl_runops_standard (/usr/lib64/libperl.so.5.26.0) [run.c:41] # Perl_call_sv (/usr/lib64/libperl.so.5.26.0) [perl.c:2848] # Perl_call_list (/usr/lib64/libperl.so.5.26.0) [perl.c:5016] # perl_destruct (/usr/lib64/libperl.so.5.26.0)
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Mark Wielaard changed: What|Removed |Added CC||fwei...@redhat.com --- Comment #5 from Mark Wielaard --- Thanks for that. This indicates that the issue is in glibc at intl/dcigettext.c around line 701 which is: /* If the current locale value is C (or POSIX) we don't load a domain. Return the MSGID. */ if (strcmp (single_locale, "C") == 0 || strcmp (single_locale, "POSIX") == 0) break; And the undefined memory came from a stack allocation at the start of this function. Which is probably this alloca: single_locale = (char *) alloca (strlen (categoryvalue) + 1); (Which isn't really at the start of the function, but I assume that is where the compiler put it.) It doesn't really make sense that this only triggers on ppc64. So I expect some ppc64 specific instruction memory tracking is going wrong in valgrind/memcheck. As far as I can see single_locale[0] is at least always defined just above this test. As long as categoryvalue was well defined. There were two recent changes to this code, although I don't think either of them should have impacted this code path: commit 9695dd0c9309712ed8e9c17a7040fe7af347f2dc Author: Florian Weimer Date: Wed Jun 21 16:31:31 2017 +0200 DCIGETTEXT: Use getcwd, asprintf to construct absolute pathname commit 37e9dc814636915afb88d0779e5e897e90e7b8c0 Author: Florian Weimer Date: Mon Jun 19 14:44:33 2017 +0200 DCIGETTEXT: Do not make copy of localename Florian, I guess I should dig into the ppc64 code and see why memcheck is not accurately tracking this. But since you recently touched this code is there any possibility this code really be an undefined memory usage? -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 --- Comment #6 from Florian Weimer --- (In reply to Mark Wielaard from comment #5) > Florian, I guess I should dig into the ppc64 code and see why memcheck is > not accurately tracking this. But since you recently touched this code is > there any possibility this code really be an undefined memory usage? The changes are supposed to be no-ops in this regard. My first guess is that due to the strcmp changes for POWER, we now have a dependency on uninitialized bytes due to word-wise memory accesses, but this does not appear in strcmp itself for some reason, only in the caller which looks at the computed result difference. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Paul Howarth changed: What|Removed |Added Blocks||1531705 --- Comment #8 from Paul Howarth --- Still failing on ppc64: https://koji.fedoraproject.org/koji/taskinfo?taskID=24037045 https://kojipkgs.fedoraproject.org/work/tasks/7045/24037045/build.log Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1531705 [Bug 1531705] [FTBFS] perl-Test-LeakTrace FTBFS rawhide -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Mark Wielaard changed: What|Removed |Added External Bug ID||KDE Software Compilation ||386945 --- Comment #9 from Mark Wielaard --- I suspect this is upstream bug https://bugs.kde.org/show_bug.cgi?id=386945 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Petr Pisar changed: What|Removed |Added See Also||https://bugzilla.redhat.com ||/show_bug.cgi?id=1532205 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Paul Howarth changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #10 from Paul Howarth --- For the moment, I have disabled the optional valgrind test on ppc64 and ppc64le, which has allowed the package to build. I would of course like to re-enable this as soon as valgrind and glibc can sort out their differences on ppc. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 --- Comment #11 from Mark Wielaard --- (In reply to Paul Howarth from comment #10) > For the moment, I have disabled the optional valgrind test on ppc64 and > ppc64le, which has allowed the package to build. I would of course like to > re-enable this as soon as valgrind and glibc can sort out their differences > on ppc. Sorry this is taking so long. There is some progress on the upstream bug https://bugs.kde.org/show_bug.cgi?id=386945 (Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7), but it isn't complete yet (it might require a slight change in code generation on the gcc side too). Should we keep this bug open till the upstream bug is resolved and backported to valgrind, or do you like me to create a new bug for that? -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test ' UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Paul Howarth changed: What|Removed |Added Version|27 |28 --- Comment #12 from Paul Howarth --- I'm fine with keeping this one open myself. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test 'UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 --- Comment #13 from Fedora Update System --- perl-Test-LeakTrace-0.16-11.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2a232d58c7 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test 'UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 --- Comment #14 from Paul Howarth --- Build on ppc64le now works on F30 and Rawhide, but still fails on F29 and presumably (haven't tested) F28. The upstream bug is closed but the fix doesn't seem to have made it into older Fedoras. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test 'UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #15 from Fedora Update System --- perl-Test-LeakTrace-0.16-11.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2a232d58c7 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1470030] perl-Test-LeakTrace-0.16-1.fc27 FTBFS: Failed test 'UninitCondition' on ppc64
https://bugzilla.redhat.com/show_bug.cgi?id=1470030 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed||2019-04-07 00:01:16 --- Comment #16 from Fedora Update System --- perl-Test-LeakTrace-0.16-11.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
