Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 697823

Summary: valgrind is changing behaviour of program
Product: Red Hat Enterprise Linux 6 Reporter: Miroslav Franc <mfranc>
Component: valgrindAssignee: Jakub Jelinek <jakub>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: law, nobody+dseketel, ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-29 17:21:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sample picture none

Description Miroslav Franc 2011-04-19 11:44:01 UTC
Created attachment 493164 [details]
sample picture

Description of problem:
On i386 valgrind doesn't behave like it should. When tried with ImageMagick's convert the program gives different outputs when run with valgrind and without. The output of the program should be the same.


Version-Release number of selected component (if applicable):
valgrind-3.6.0-3.el6.i686


How reproducible:
always


Steps to Reproduce:
1. convert -radial-blur 5 munich.jpg 0munich.jpg
2. valgrind convert -radial-blur 5 munich.jpg 1munich.jpg
3. md5sum [01]munich.gif


Actual results:
md5sums are different


Expected results:
md5sums are the same


Additional info:
1/ The sample picture used is in attachment.
2/ So far seems to be limited to i386 arch.
3/ This is most likely issue on rawhide and previous version as well.
4/ Other reproducers:
convert -equalize munich.jpg 0munich.gif
convert -posterize 10 munich.jpg 0munich.jpg
convert -posterize 10 munich.jpg 0munich.png
convert -posterize 10 munich.jpg 0munich.gif
convert -flop munich.jpg 0munich.gif
convert -flip munich.jpg 0munich.gif
convert -resize 50\% munich.jpg 0munich.gif
convert -radial-blur 5 munich.jpg 0munich.gif
convert -resize 160x100 munich.jpg 0munich.gif
5/ In some cases you can use ImageMagick's compare instead of md5sum, to verify the images are different visually.

Comment 2 Jakub Jelinek 2011-04-19 12:31:02 UTC
Might very well be e.g. https://bugs.kde.org/show_bug.cgi?id=197915 which isn't likely to be fixed any time soon.

Comment 6 Jeff Law 2012-05-29 17:21:26 UTC
Given the trend towards using the SSE units rather than the x87 FPU, properly modeling the x87 FPU just isn't going to be terribly important.  Given the amount of work necessary and the declining importance, I don't see how we can justify the engineering effort to address this isue.

Closing as WONTFIX.