Re: fontconfig 2.8.0

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Derek Leach wrote:
Hello All,

I have encountered a bug on a internal distribution that uses fontconfig
2.8.0, the backtrace is identical to this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=532718

at least frames #0 - #7.  I have been trying to find the code change
that fixed this bug, but have not been successful.

Can someone direct me to the code change that was used to fix this segfault?


Judging by the date of the comments in this bug I would guess 1f4e6fecde22fd4ce8336b01a5c32c533fcb8bac, i. e.
http://cgit.freedesktop.org/fontconfig/commit/?id=1f4e6fecde22fd4ce8336b01a5c32c533fcb8bac

However, if I understand the bug correctly this was supposed to be fixed with 2.8.0, and even before only happened if the same cache was used by different fontconfig versions. Are you sure it's what you're seeing?

Raimund

--
Worringer Str 31 Duesseldorf 40211 DE  home: <rs@xxxxxxxx>
+49-179-2981632 icq 16845346           work: <rs@xxxxxxxxxxxxxxx>
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig




[Index of Archives]     [Fedora Fonts]     [Fedora Users]     [Fedora Cloud]     [Kernel]     [Fedora Packaging]     [Fedora Desktop]     [PAM]     [Gimp Graphics Editor]     [Yosemite News]

  Powered by Linux