[XeTeX] Segmentation fault with xdvipdfmx

[Ralf Stubner]

Hi,

I am using the 'macosx' branch of xdvipdfmx (revision 54) and get a
segmentation fault from xdvipdfmx when processing the following file: 

\font\x="Palatino Linotype:+smcp"
\x abc
\bye

(Palatino Linotype as shipped with WinXP). Output from xdvipdfmx:

$ xdvipdfmx -vv pala.xdv 
DVI Comment:  XeTeX output 2006.07.10:0946
pala.xdv -> pala.pdf
[1<PalatinoLinotype-Roman(Palatino Linotype:Regular)@9.96pt<NATIVE-FONTMAP:PalatinoLinotype-Roman>
fontmap: PalatinoLinotype-Roman -> /home/ralf/.fonts/pala.ttf(Identity-H)

pdf_font>> Input encoding "Identity-H" requires at least 2 bytes.
pdf_font>> The -m <00> option will be assumed for "/home/ralf/.fonts/pala.ttf".
(CID:PalatinoLinotype-Roman)
pdf_font>> Type0 font "/home/ralf/.fonts/pala.ttf" cmap_id=<Identity-H,0> opened at font_id=<PalatinoLinotype-Roman,0>.
><cmr10 at 9.96pt(TFM:cmr10[/usr/share/texmf-tetex/fonts/tfm/public/cm/cmr10.tfm])
fontmap: cmr10 -> cmr10[remap]

pdf_font>> Simple font "cmr10" enc_id=<builtin,-1> opened at font_id=<cmr10,1>.
>](cmr10[CMR10][built-in][Type1][2 glyphs][328 bytes])
otf_cmap>> Creating ToUnicode CMap for "/home/ralf/.fonts/pala.ttf"...
Segmentation fault

There is no such problem if I leave out the ':+smcp'. I have seen this
only with Palatino Linotype, which is special since it has the small
caps unencoded and not in the PUA as my other fonts. 

cheerio
ralf