[Fontconfig] fontconfig 2.8.0
DLeach at qnx.com
Thu Apr 3 06:39:32 PDT 2014
I am double checking the version on the customer's install, will get back to you.
The call stack is identical in the last seven frames, though pango is not involed in this particular call stack.
From: Raimund Steger [mailto:rs at mytum.de]
Sent: April-02-14 6:18 PM
To: Derek Leach; 'fontconfig at lists.freedesktop.org'
Subject: Re: [Fontconfig] fontconfig 2.8.0
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:
> 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.
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?
Worringer Str 31 Duesseldorf 40211 DE home: <rs at mytum.de>
+49-179-2981632 icq 16845346 work: <rs at interface-ag.de>
More information about the Fontconfig