Bug 754688
Summary: | Invalid memory access in Fontconfig | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andris Pavenis <andris.pavenis> |
Component: | fontconfig | Assignee: | Matthias Clasen <mclasen> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | behdad, fedora-bugzilla-odin, fonts-bugs, pnemade, tagoh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-01-12 01:17:44 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: |
Description
Andris Pavenis
2011-11-17 11:12:41 UTC
I think this has already been fixed in upstream by: http://cgit.freedesktop.org/fontconfig/commit/?id=1c475d5c8cb265ac939d6b9e097666e300162511 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. valgrind error in fontconfig are generally due to valgrind not understanding fontconfigs caches Re Comment #:1 F16 includes this fix from what I can see. The debuginfo shows the code in the patch that supposidly fixes this upstream. Also note the error is that it is accessing a 4 byte range at byte 20 into block of 22. I would guess that this isn't being allocated inside the method due to the missing symbol "???". I am claiming (with this comment) that the allocation of the memory is not happening inside "FcConfigFileExists" where the patch linked in Comment #:1 to round up the malloc call to a even size of 4 bytes is already included in F16. Therefore it would have been an allocation of 24 bytes if that code path did the allocation, gdb shows the source to have the patch change included in the F16 release but still the same valgrind invalid read-4 output happens as show in the original bug report. My valgrind runs are from May 2012. fontconfig-2.8.0-4.fc16.x86_64 I also do not think this has anything to do with caches the full valgrind backtrace shows up it is part of the configuration parsing and in the methods being called (listed in the valgrind report) the code is mainly manipulating a full pathnames. (In reply to comment #4) > Re Comment #:1 F16 includes this fix from what I can see. > The debuginfo shows the code in the patch that supposidly fixes this > upstream. That change has been made in 2.9.0. if you doubt you can try it again on rawhide, where 2.9.0 is available. |