[XeTeX] [SOLVED] Segmentation fault error in xdvipdfmx 0.7.8 with CharisSIL 4.106

Wilfred van Rooijen wvanrooijen at yahoo.com
Thu Feb 4 00:42:25 CET 2010

> Is it likely that the error was not with the font being
> damaged
> when it affected only one font when used in one
> program?  Wouldn't
> I notice in a lot of ways if the memory were damaged?

Not necessarily. I am not an expert on computer memory architecture, but my understanding of memory management is the following. Memory is handed out in pages, which are fixed size chunks. An application will request N pages, get N pages from the OS, but may not use all of these pages. So, if a bad memory is inside one of those allocated pages but not being used, you would probably never notice. But I would expect that indeed you would have noticed a bad memory much earlier.


> I have solved the problem, by any or all of the following:
> erasing all copies of CharisSIL font files and archives on
> my system, of which there turned out to be only one each,
> thereafter downloading a fresh copy of the font files from
> the SIL site, unpacking and installing it -- for the third
> time!
> -- then running fc-cache -f (where -f probably is the
> operative thing which I wasn't aware of previously). 
> Another factor also
> came to my memory: last week I opened the CharisSIL-Regular
> font file with FontForge to check out some glyph
> variants.  Is it
> possible that I damaged the file when doing so?  It
> seems clear
> the font file, or the fc-cache data on it, was damaged in
> some
> way.  Although the problem is now gone I wish I knew
> what it was,
> so that I (or someone else) will not repeat it.
> Thanks for taking the time, George and Wilfred.
> /BP
> --------------------------------------------------
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex

      Get your new Email address!
Grab the Email name you've always wanted before someone else does!

More information about the XeTeX mailing list