[XeTeX] XeTeX .92: *** unexpected DVI command: -1 Segmentation fault

[Jonathan Kew]

(Copying to the list so others can be aware of the status...)

Thanks for the [off-list] test file, that's very helpful.

You've found a nice shiny new bug of your very own here, freshly minted 
for release 0.92. :-) Reverting to 0.91 avoids the issue, so if you 
like you could grab that installer off the "version history" page and 
use it for now. But I'll aim to produce 0.93, including a fix for this, 
once I get back to the office tomorrow.

The fragment that actually triggers the crash is "\text{ or }", which 
you have in a couple of your displayed equations. To be exact, it's the 
trailing space here that causes the problem. If you replace "\text{ or 
}" with "\text{ or~}" (i.e., make that a non-breaking "tie" space)--and 
any other similar cases--it won't crash.

All this is a result of my attempt to fix the version 0.9 problem with 
right-to-left AAT fonts, reported by Otared Kavian; that involved 
restructuring the AAT layout code, and clearly I got it slightly wrong. 
My apologies!

JK

On 9 Mar 2005, at 6:36 pm, Roger Hart wrote:

> Dear Jonathan,
>
> As always, thanks for your expert help. Here's a simple file that 
> causes the crash, though I can't determine why. It compiles fine 
> without Hoefler and fontspec:
>
> <crash-test.tex>
>
> I've also appended the crash.log file, if it is of any help.
>
> Thanks so very much,
>
> Roger
>
>
>>> Today I updated my TeX installation using i-Installer (2004 stable, 
>>> full install) and then re-installed XeTeX .92.  In running a file 
>>> which previously worked just fine, I get the following message:
>>>
>>> *** unexpected DVI command: -1
>>> Segmentation fault
>>>
>>> I'm afraid that the DVI command is even more unexpected for me than 
>>> for XeTeX.  Any suggestions?
>>
>> A couple of suggestions: See if you can narrow things down to a 
>> particular "problem section" of your file (a certain figure, 
>> equation, paragraph, or something) that you could send me for 
>> testing--preferably with a cut-down preamble that doesn't load dozens 
>> of packages, etc.--so that I can reproduce the failure here.
>>
>> And check in ~/Library/Logs/CrashReporter for a xelatex.crash.log 
>> file, and feel free to email me the last crash report from it. (A new 
>> report will be appended to that file each time xelatex crashes, and 
>> they'll probably all have similar content. The most relevant part is 
>> usually the backtrace, under the heading "Thread 0 Crashed".
>
> **********
>
> Host Name:      rhart.local
> Date/Time:      2005-03-09 12:33:55 -0600
> OS Version:     10.3.8 (Build 7U16)
> Report Version: 2
>
> Command: xelatex
> Path:    /usr/local/teTeX/bin/powerpc-apple-darwin-current/xelatex
> Version: ??? (???)
> PID:     1281
> Thread:  0
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x83c4740c
>
> Thread 0 Crashed:
> 0   xelatex 	0x0003010c hlistout + 0x26c (xetex1.c:5057)
> 1   xelatex 	0x0003140c hlistout + 0x156c (xetex1.c:5459)
> 2   xelatex 	0x0003140c hlistout + 0x156c (xetex1.c:5459)
> 3   xelatex 	0x000327bc vlistout + 0x2dc (xetex1.c:5997)
> 4   xelatex 	0x000327b4 vlistout + 0x2d4 (xetex1.c:5995)
> 5   xelatex 	0x000327b4 vlistout + 0x2d4 (xetex1.c:5995)
> 6   xelatex 	0x00033580 zshipout + 0x754 (xetex1.c:6348)
> 7   xelatex 	0x0004d024 maincontrol + 0x714 (xetex2.c:7365)
> 8   xelatex 	0x00011314 mainbody + 0x246c (xetexini.c:4870)
> 9   xelatex 	0x0004ffd4 main + 0x14 (xetexextra.c:384)
> 10  xelatex 	0x00002244 _start + 0x188 (crt.c:267)
> 11  dyld    	0x8fe1a558 _dyld_start + 0x64
...<snip>...