<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>Seg fault with Charis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I'm having a problem with xetex giving me a segmentation fault, and<BR>
I'd appreciate any advice that someone could give.<BR>
<BR>
I have Ubuntu Feisty, with the latest TeXLive.<BR>
<BR>
I am trying to use Charis (I need boldface and latin 1, and I admire<BR>
the way it looks). I have the latest version and I believe that I<BR>
have it installed correctly; for instance I see it in my font directory.<BR>
<BR>
I am generating reports from a database. The top of each report looks like<BR>
this:<BR>
\documentclass[11pt]{report}<BR>
<BR>
\usepackage{fontspec}<BR>
\usepackage{xunicode}<BR>
\usepackage{xltxtra}<BR>
\setmainfont{CharisSIL}<BR>
If I run a small report, say of 8 pages, it runs fine. I am using longtable<BR>
so I have to run xelatex twice, and it looks great.<BR>
<BR>
Now I switch to a 1500 page report (there are more than 1000 longtables).<BR>
The first pass is great. I can view it and it looks fine. But I need a<BR>
second pass. That turns out not so well. Here is the last few lines of<BR>
the run:<BR>
<BR>
Overfull \hbox (7.68636pt too wide) detected at line 816<BR>
[]\EU1/CharisSIL(0)/m/n/10.95 1337<BR>
<BR>
Overfull \hbox (7.68636pt too wide) detected at line 820<BR>
[]\EU1/CharisSIL(0)/m/n/10.95 1344<BR>
<BR>
Overfull \hbox (7.68636pt too wide) detected at line 823<BR>
[]\EU1/CharisSIL(0)/m/n/10.95 1349<BR>
) [5] [6]Segmentation fault<BR>
jim@millstone:/home/sphyg/trunk/bin/latex$<BR>
Output file removed.<BR>
<BR>
It always fails in the same place. The log file contains roughly the<BR>
same output.<BR>
<BR>
Running the same file with Gentium and two passes works great. Running the<BR>
same file with Gentium twice, and then Charis gives the above error. That<BR>
makes me suspect that the sheer size is a problem. Possible?<BR>
<BR>
Here are the file sizes.<BR>
$ ls -l College*<BR>
-rw-r--r-- 1 jim jim 160986 2007-11-09 20:19 College_1.aux<BR>
-rw-r--r-- 1 jim jim 36349 2007-11-09 20:19 College_1.idx<BR>
-rw-r--r-- 1 jim jim 222656 2007-11-09 20:19 College_1.log<BR>
-rw-r--r-- 1 jim jim 10743 2007-11-09 20:19 College_1.out<BR>
-rw-r--r-- 1 jim jim 3534170 2007-11-09 20:19 College_1.pdf<BR>
-rw-r--r-- 1 jim jim 1973494 2007-11-09 20:13 College_1.tex<BR>
-rw-r--r-- 1 jim jim 1973448 2007-11-08 21:10 College_1.tex~<BR>
-rw-r--r-- 1 jim jim 44931 2007-11-09 20:19 College_1.toc<BR>
<BR>
If anyone has any debugging ideas, I'd be glad to hear them. I am<BR>
ignorant of where to start, I admit. Looking at the archives<BR>
of this list, I saw a message a few months back about a seg fault<BR>
and Charis, but it seemed to involve small caps, and I don't see why<BR>
a small document would run but not a large one (both contain small<BR>
caps). But I could be wrong of course. I'd be happy to supply<BR>
the large file if that would help.<BR>
<BR>
Thanks,<BR>
Jim Hefferon<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>