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/