This is the mail archive of the
cygwin-xfree
mailing list for the Cygwin XFree86 project.
Re: coredumps with fc-cache, fc-list
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: "cygwin-xfree at cygwin dot com" <cygwin-xfree at cygwin dot com>
- Date: Tue, 28 Aug 2012 03:26:18 -0500
- Subject: Re: coredumps with fc-cache, fc-list
- References: <503C61C2.2010406@cwilson.fastmail.fm>
- Reply-to: cygwin-xfree at cygwin dot com
On Tue, 2012-08-28 at 02:14 -0400, Charles Wilson wrote:
> The (re)build of fontconfig-2.8.0-2 went fine, but when setup installed
> it, I got an error during postinstall. Setup.log.full says:
>
> 2012/08/28 01:38:48 running: C:\cygwin-1.7\bin\bash.exe --norc
> --noprofile "/etc/postinstall/fontconfig.sh"
> /etc/postinstall/fontconfig.sh: line 2: 4164 Segmentation fault
> (core dumped) /usr/bin/fc-cache -r
WFM.
> I next ran 'fc-cache -fsv' as Adminstrator, and everything went
> swimmingly...until I got to the Windows dir:
> ...
> /cygdrive/c/Windows/Fonts: Segmentation fault (core dumped)
>
> FWIW, I have 469 true type fonts in Windows/Fonts. There are a mixture
> of fonts identified by Windows as "TrueType" and "OpenType" even tho
> they all end in .ttf. Three of the font files have spaces in their names.
> /cygdrive/c/Windows/Fonts/Envy Code R Bold.ttf
> /cygdrive/c/Windows/Fonts/Envy Code R Italic.ttf
> /cygdrive/c/Windows/Fonts/Envy Code R.ttf
> I tried removing those three offenders, just in case, and re-running
> fc-cache but it still dumped core.
>
> Any ideas?
Fontconfig is WJFFM (Win7 x64, 290 .ttf files in Windows fontdir, none
with spaces). I suspect you have a corrupt or otherwise incorrect font
file in your Windows fontdir. What happens if you remove that directory
from /etc/fonts/fonts.conf? Can you try to narrow it down further to a
specific font file?
Yaakov
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/