Created attachment 410155 [details] valgrind dynbss patch +++ This bug was initially created as a clone of Bug #539874 +++ valgrind fails with Assertion 'di->bss_size == shdr->sh_size' failed. Version-Release number of selected component (if applicable): valgrind-3.5.0-1.el5 libvirt-0.6.3-33.el5 How reproducible: Always. Steps to Reproduce: valgrind -v --leak-check=full --show-reachable=yes --log-file=libvirtd.memcheck /usr/sbin/libvirtd Actual results: valgrind: m_debuginfo/readelf.c:1901 (vgModuleLocal_read_elf_debug_info): Assertion 'di->bss_size == shdr->sh_size' failed. ==18688== at 0x38029D5C: ??? (in /usr/lib64/valgrind/memcheck-amd64-linux) Expected results: No crash. Additional info: valgrind-3.5.0-dynbss.patch from RHEL 6.0 Beta SRPM fixes the problem.
Created attachment 410162 [details] valgrind dynbss patch This patch cleans up the line numbers to fix the patch fuzziness.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When testing prelinked programs, valgrind could have crashed due to a segmentation fault due to a failed assertion. This was caused by the prelink utility handling the .bss section incorrectly. This update corrects this assertion so that it no longer fails in the described scenario.
s/due to a segmentation fault // ? Possibly s/crashed/exited unexpectedly/ ?
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1026.html