[XeTeX] Segmentation fault
Malcolm.Ross at anu.edu.au
Tue Jul 26 16:57:33 CEST 2005
Many thanks, Jonathan, for the suggestion about bad fonts. You were
right, and my problem is solved. ( I was editing someone else's paper
and had installed a phonetic font that came with it in order to read
it. I had forgotten that I had done this when I said that nothing had
changed since my previous use of XeTeX.) I have now reinstalled XeTeX
0.94, and it is running correctly (and so is Word!).
And thank you, too, Bruno and Peter, for your help. I have learned a
little more about how to use the Console to locate log files, thanks to
On 26/07/2005, at 2:33 PM, Jonathan Kew wrote:
> On 26 Jul 2005, at 6:45 am, Bruno Voisin wrote:
>> Le 26 juil. 05 à 12:01, Malcolm Ross a écrit :
>>> I am taking the liberty of sending this direct to you, not to the
>>> list, as there is an attachment. Many thanks for your helpful
>>> message. I have done what you suggested, and the Console crash
>>> messages and the XeTeX crash log are in the attached file. I have
>>> looked at them, but I have little idea what they mean. Any advice
>>> would be greatly appreciated.
>>> Is it possible hat I have a hardware fault?
>> I am cc'ing this to the XeTeX list, since the problem looks like a
>> XeTeX bug.
>> This extract from your xelatex.crash.log:
>>> Exception: EXC_BAD_ACCESS (0x0001)
>>> Codes: KERN_INVALID_ADDRESS (0x0001) at 0x0890c000
>>> Thread 0 Crashed:
>>> 0 ATS 0x96c1aa0c FixPostScriptName + 0x128
>>> 1 ATS 0x96c19598 FOGetNameInternal + 0x2a4
>>> 2 ATS 0x96c0ae70 _eFOGetName + 0x288
>>> 3 ATS 0x96c0abc4 FOGetName + 0x60
>>> 4 com.apple.QD 0x915b7c64 ATSUGetIndFontName + 0xa0
>>> 5 xelatex 0x000567d8 init_font_dicts() + 0x1a0
>>> 6 xelatex 0x00057060 find_font_by_name + 0x3c
>>> 7 xelatex 0x00054484 findatsufont + 0x11c (xetexmac.c:836)
>>> 8 xelatex 0x0002baa8 zloadnativefont + 0x8c
>>> 9 xelatex 0x0002c290 zreadfontinfo + 0x84 (xetex1.c:3334)
>>> 10 xelatex 0x00049b60 znewfont + 0x414 (xetex2.c:5922)
>>> 11 xelatex 0x00009444 prefixedcommand + 0x15bc
>>> 12 xelatex 0x0004d704 maincontrol + 0xbf0 (xetex2.c:7731)
>>> 13 xelatex 0x00011510 mainbody + 0x246c (xetexini.c:4870)
>>> 14 xelatex 0x000501d8 main + 0x14 (xetexextra.c:384)
>>> 15 xelatex 0x00002440 _start + 0x188 (crt.c:267)
>>> 16 dyld 0x8fe1a558 _dyld_start + 0x64
>> looks suspiciously like one reported earlier on 9 March in a thread
>> "XeTeX .92: *** unexpected DVI command: -1 Segmentation fault":
> No, this is unrelated; it's crashing in a completely different place.
> This looks to me like a case of "bad font". Have you added any fonts
> anywhere in your system lately? I believe there's a font with a bad or
> missing entry in the internal name table, and this is crashing Apple
> Type Services when it tries to collect information on all the
> available fonts.
> This could well also be giving you problems in Word, e.g., when it
> tries to build its Font menu.
> To track down the offending font, you'll probably need to experiment
> with removing non-standard fonts (from /Library/Fonts,
> ~/Library/Fonts, or your Classic Fonts folder) until you isolate the
> one that's causing trouble.
More information about the XeTeX