On 1/1/2016 5:31 AM, Michal Hoftich wrote:
Hi Nasser,
it seems that it is caused by the xfrac package. A really minimal
example is following:
\documentclass[12pt]{report}%
\usepackage[T1]{fontenc}
\usepackage{xfrac}
\begin{document}
\[ \sfrac{a}{b} \]
\end{document}
On 1/1/2016 3:08 PM, Michal Hoftich wrote:
Thanks but I am not getting the core dump on my end? TL 2015
fresh update.
That's weird, I have freshly updated TL as well..
If you like me to try something else, please let me know.
I've got the SIGSEGV error also with your sample file
That
> Thanks but I am not getting the core dump on my end? TL 2015
> fresh update.
>
That's weird, I have freshly updated TL as well..
>
> If you like me to try something else, please let me know.
I've got the SIGSEGV error also with your sample file
>
> btw, there is new version of dvisvgm by
I'm not sure if you determined if all of this is a dvisvgm bug,
but if not:
Here is a MWE, which shows the issue. What happens is that
DVI creates corrupted DVI file or has an error making the dvi.
When dviluatex (or any engine) creates a corrupted DVI file (i.e.,
dvitype cannot
>
> No. dvisvgm needs to be build from sources for Linux which I
> did not do. Still using TL 2015 version. 1.9.2 as is.
>
I have the same version
>
> You might be using different build of dvisvgm, i.e. different OS
> and this could cause this difference?
>
I am using Fedora 23, but binaries
Hi Nasser,
it seems that it is caused by the xfrac package. A really minimal
example is following:
\documentclass[12pt]{report}%
\usepackage[T1]{fontenc}
\usepackage{xfrac}
\begin{document}
\[ \sfrac{a}{b} \]
\end{document}
compiled with
latex minimal.tex
dvisvgm
This is follow up on the make4ht errors I was getting,
"max_count exceeded". But since I finally found the conflict
that was causing it, and it is all related to DVI problems,
I thought to start new thread.
Here is a MWE, which shows the issue. What happens is that
DVI creates corrupted DVI
