[XeTeX] segmentation fault

[Yves Codet]

Hello Jonathan.

Le 2 juil. 06 à 16:57, Jonathan Kew a écrit :

> The crash log indicates that it is crashing within an Apple Type
> Services routine; this could indicate a corrupted or buggy font file,
> or it could indicate that xetex is calling the routine with bad data
> (due to a bug in xetex itself).
>
> Two things to look into: (1) What font(s) are you using, and does the
> problem go away if you specify different fonts? (2) If you can't
> narrow it down to one particular font, then please create and send me
> a small test document with the minimum packages needed to cause the
> crash.

I was using Charis SIL 4.0.02.r1. I've tried a few system fonts,  
randomly. There's no problem with Lucida Grande, Monaco, Helvetica;  
but XeTeX crashes with Zapfino, Courier, Times as well. Here is a  
short sample which should show that behaviour:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.tex
Type: application/octet-stream
Size: 565 bytes
Desc: not available
Url : http://tug.org/pipermail/xetex/attachments/20060702/e7e6958e/attachment.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: comment.tex
Type: application/octet-stream
Size: 11994 bytes
Desc: not available
Url : http://tug.org/pipermail/xetex/attachments/20060702/e7e6958e/attachment-0001.obj 
-------------- next part --------------

As you guessed the first file calls the other one. What is strange is  
that if I comment out the lines concerning Devanagari MT, which is  
not used in this part of the text anyway, there's no crash. That's  
why I'm unable to say that such and such font is the culprit. Thanks  
for your help.

Best wishes,

Yves