Menu
▾
▴
#386 XDvi 22.84.9 (Xaw toolkit): Failed assertion
$> xdvi pages.dvi
************************************************************
XDvi 22.84.9 (Xaw toolkit): Failed assertion:
dvi-draw.c:5928: "G != NULL": T1_SetChar() returned NULL
Aborting now. Please report this as a bug to:
http://sourceforge.net/tracker/?group_id=23164&atid=377580
If a core dump has been produced, please invoke:
gdb xdvi-xaw3d.bin core
Then type "bt", and include the resulting output in your bug report.
************************************************************
Char "y": DoClosePath: No previous point!Aborted
Can you send the file pages.tex (or at least pages.dvi)? Otherwise debugging would not be possible.
Yeah, sorry bit lazy in my initial report. I have included some text below that reproduces the problem. It is definitely related to the cmbxsl font. On my system I have a file called /usr/share/texmf/fonts/type1/bluesky/cm/cmbxsl10.pfb. If I remove that file, xdvi works fine, but does report:
xdvi-xaw3d.bin: Warning: Font map calls for cmbxsl10.pfb, but it was not found (will try PK version instead).
Not every document or occurrence of this font causes the problem. I have many other documents using the same fondt for highlighting that continue to work fine.
\documentclass{article}
\font\bl=cmbxsl10
\begin{document}
The above sets (both finite and infinite) have all been {\bl
explicitly\/} defined (also called a {\bl definition by extension}, in
that we directly listed all the members of the set. It is also
possible to {\bl implicitly\/} define a set with a logical statement
in any language.
\end{document}
> uname -a
Linux xxx 2.6.18-128.1.14.el5 #1 SMP Wed Jun 17 06:38:05 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
CentOS 5.8 (Final)
I cannot reproduce the bug. However, the bug occurs in the part of xdvik that accessed the t1lib library. Xdvi now uses the freetype library to handle PostScript Type 1 fonts, and the code for handling those fonts was rewritten in 2012. So it is most likely that the bug went away during that transition. Please reopen the bug or submit a new one if the problem persists using a more recent version of xdvi.