Bug 700801 - running valgrind on totem with malicious file "crash"
Summary: running valgrind on totem with malicious file "crash"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: dbus
Version: 4.9
Hardware: ppc
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Zeuthen
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-29 12:46 UTC by Tomas Pelka
Modified: 2013-03-06 04:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:25:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Tomas Pelka 2011-04-29 12:46:48 UTC
Description of problem:
With crash I meant that valgrind terminated immediately after initialization on PPC only.

"Crash" seems to be related to dbus.

See http://nest.test.redhat.com/mnt/qa/scratch/ppcp-4as-v1/2011:11132/tps/gstreamer.vg.16233.oldpkg and http://nest.test.redhat.com/mnt/qa/scratch/ppcp-4as-v1/2011:11132/tps/gstreamer.vg.16323.newpkg


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. see https://bugzilla.redhat.com/show_bug.cgi?id=695420#c10 
2.
3.
  
Actual results:
crash described in description

Expected results:
no described "crashes"

Additional info:
Not a regression reproducible on gstreamer-plugins-0.8.5-1.EL.3 and gstreamer-plugins-0.8.5-1.EL.2.
Reproducible only on ppc.

Comment 1 Jiri Pallich 2012-06-20 13:25:13 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.