RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Trying to build netcdf for EPEL 6 and it fails on pp64.  Task is here:

http://koji.fedoraproject.org/koji/taskinfo?taskID=2192605

First it runs a series of tests, and then it runs them under valgrind.  Tests run fine without valgrind, but segfault under valgrind.  I don't have access to a ppc64 machine at the moment to test with.

Version-Release number of selected component (if applicable):
valgrind-3.5.0-12.el6

Just rerun the failed test under valgrind without -q from the spec file, that will
print out the problem.  An application bug is far more probable than valgrind bug here.  When valgrind segfaults, most of the time it just means the application segfaulted, say accessing a freed block etc.  valgrind message should contain enough info to fix it.

I can't reproduce this anymore.