dvipng
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Dvipng] DVIPNG segfault on DVI output of simple TEX file?


From: Jan-Åke Larsson
Subject: Re: [Dvipng] DVIPNG segfault on DVI output of simple TEX file?
Date: Mon, 17 Jun 2013 07:24:52 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6

There isn't much traffic these days, I dont have much time to put either.

The below works for me (linux mint) so either there is a build problem or something to do with your setup.

In any case, it is a standard image, so if that doesn't work, then nothing will. I would have many bug reports if everyone sees this.

Have you tried adding -d?

Perhaps it needs a newer kpathsea, but doesn't say so in the dependencies?

Best,
/JÅ


On 2013-06-17 07:10, Shriramana Sharma wrote:
Hello. The last post on this list was from last year but I hope people
are still around:

I'm running Kubuntu Raring, with versions as below:
texlive-base: 2012.20120611-5
dvipng: 1.14-1build1

I have this simple document foo.tex:

\documentclass[16pt]{article}
\usepackage{amsmath,amssymb}
\usepackage{breqn}
\pagestyle{empty}
\begin{document}
$ \infty $
\end{document}

I do latex foo.tex and I get the .dvi files with no problems. Then I do:

dvipng -T tight -D 150 -bg Transparent -fg Blue -O 0cm,0cm foo.png foo.dvi

I get this:

This is dvipng 1.14 Copyright 2002-2010 Jan-Ake Larsson
Segmentation fault (core dumped)

gdb says there are no debugging symbols so I couldn't try that.

Due to this dvipng problem I am not able to use SymPyPrt on
IPython2/3: https://groups.google.com/d/msg/sympy/WzwS3578TuU/sZAYDcFQ8cIJ

I did not have a problem with using SymPyPrt on Kubuntu Precise of
last year, and dvipng has practically not changed in Raring since
Precise: 
http://packages.ubuntu.com/search?keywords=dvipng&searchon=names&suite=all&section=all
except for a new build. The changelog
http://changelogs.ubuntu.com/changelogs/pool/main/d/dvipng/dvipng_1.14-1build1/changelog
says it's for some kpathsea transition but I'm not sure whether that
would be the cause of the problem.

I hope Jan or someone else can help me. Thank you!





reply via email to

[Prev in Thread] Current Thread [Next in Thread]