coredumps with fc-cache, fc-list

coredumps with fc-cache, fc-list

[Charles Wilson]

While trying to debug the problem with my new build of rxvt-unicode, I 
find that I am getting a segfault way down deep in libfreetype. I 
rebuilt libfreetype with the new cygport, so I could get those handy 
debug symbols, and spent some time trudging thru that.

Then, since libfreetype is actually called by libfontconfig, and not 
directly by rxvt-unicode, I decided to download the -src package and 
rebuild THAT, too -- again, so I could have debug symbols for a few of 
my intervening stack frames.

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

Ick.  So, I reinstalled the "real" version...and I got the same message:

2012/08/28 01:53:01 running: C:\cygwin-1.7\bin\bash.exe --norc 
--noprofile "/etc/postinstall/fontconfig.sh"
/etc/postinstall/fontconfig.sh: line 2:  6856 Segmentation fault 
(core dumped) /usr/bin/fc-cache -r


Running 'fc-list : family' also coredumps (using the official 
fontconfig-2.8.0-2).

*=-=-=-=-=-=-=-=-=*
I next ran 'fc-cache -fsv' as Adminstrator, and everything went 
swimmingly...until I got to the Windows dir:

...
/usr/share/texmf-dist/fonts/type1/urw/times: caching, new cache 
contents: 4 fonts, 0 dirs
/usr/share/texmf-dist/fonts/type1/urw/zapfchan: caching, new cache 
contents: 1 fonts, 0 dirs
/usr/share/texmf-dist/fonts/type1/urw/zapfding: caching, new cache 
contents: 1 fonts, 0 dirs
/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? I'm going to try, just for grins and giggles, installing a 
self-built version of fontconfig-2.10.$latest and see if that helps 
matters...but I won't be able to do so until Thursday at the earliest.
--
Chuck

--
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/

Re: coredumps with fc-cache, fc-list

[Yaakov (Cygwin/X)]

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/

Re: coredumps with fc-cache, fc-list

[Charles Wilson]

On 8/28/2012 4:26 AM, Yaakov (Cygwin/X) wrote:
> 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?

Yes, that was it. The Thai font Angsana New (Regular) was corrupt; 
removing it and all the other Angsana TTF files fixed that problem.  Now 
I'm back to debugging, on the Vista machine where gdb actually works 
[1], the original problem with rxvt-unicode which I encountered on W7 -- 
that is, whenever I do anything "interesting" (like, say, simply 
starting vi), my rxvt-unicode terminal crashes with a SIGABRT:

Program received signal SIGABRT, Aborted.
0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x77015490 in ntdll!ZwWaitForSingleObject ()
    from /c/Windows/system32/ntdll.dll
#2  0x757b9aa4 in WaitForSingleObjectEx ()
    from /c/Windows/system32/kernel32.dll
#3  0x00000564 in ?? ()
#4  0x00000000 in ?? ()


No idea why. I have debugging symbols available but...the abort appears 
to occur down in ntdll somewhere, and I have nothing informative in the 
remaining backtrace. Sigh.  I'm pretty much stumped at this point; my 
next try will be to build a completely minimal, zero frills, version and 
see if it works better. If so, then slowly add features back...

[1] "Space key + gdb": http://cygwin.com/ml/cygwin/2012-08/msg00571.html

--
Chuck

--
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/