[XeTeX] Fwd: Re: Segmentation fault in xdvipdfmx

[Jonathan Kew]

Sorry, Mike, I haven't had any time to look into this. (Of course, if  
someone else is able to dig in to the code and font, to figure out  
what's breaking, that'd be great.)

There have been a few bug-fixes in xdvipdfmx that will go into the  
TL'09 release, but I don't know if they're relevant to your particular  
failure or not. There were some issues related to reading fonts, so  
it's possible one of these may have been causing the crash. If you're  
able to rebuild from the latest source (from either the xetex or  
texlive repositories), you could see if that makes any difference.

JK


On 12 Jun 2009, at 16:21, maxwell wrote:

> I don't mean to nag, but is there any chance of getting this fixed?   
> Or is
> it a bug in the font?
>
>   Mike Maxwell
>
> -------- Original Message --------
> Subject: Re: [XeTeX] Segmentation fault in xdvipdfmx
> Date: Thu, 04 Jun 2009 16:44:59 -0400
> From: maxwell <maxwell at umiacs.umd.edu>
> To: Unicode-based TeX for Mac OS X and other platforms <xetex at tug.org>
> Reply-To: Unicode-based TeX for Mac OS X and other platforms
> <xetex at tug.org>
>
> On Mon, 01 Jun 2009 18:36:54 -0400, maxwell <maxwell at umiacs.umd.edu>  
> wrote:
>> On Sun, 31 May 2009 16:28:42 +0100, Jonathan Kew
> <jfkthame at googlemail.com>
>> wrote:
>>> Any chance of narrowing down the range of
>>> your document that (sometimes) leads to the crash, perhaps by  
>>> repeated
>>> bisection?
>
> OK, I think the attached file is pretty much minimal, and it seems to
> reproduce the problem consistently.  It's possible that the crash  
> happens
> when a character inside the \urdu{...} is not present in the Urdu  
> font; at
> least I see a '!' in there, and when I delete that, I get a warning  
> msg in
> place of a crash.
>
>   Mike Maxwell<UrduGrammar.xetex>