search

mgieseki / dvisvgm

A fast DVI, EPS, and PDF to SVG converter
https://dvisvgm.de
GNU General Public License v3.0
307 stars 34 forks source link

Crashed: Windows/TexLive+babel[russian] #27

Closed mgieseki closed 10 years ago

mgieseki commented 10 years ago

dvisvgm 1.0.5 22534, Windows, Texlive.

Crashed (segfault) on latex files, where \usepackage[russian]{babel}.

Minimal sample attached.

Launchpad Details: #LP925197 sfomin - 2011-05-27 19:18:00 +0200

mgieseki commented 10 years ago

Commands to reproduce the bug:

latex.exe bug.tex dvisvgm --exact -TS1.5 --no-fonts --bbox=min --output="%f-%p.svg" bug.dvi

Launchpad Details: #LPC sfomin - 2011-05-27 19:19:00 +0200

mgieseki commented 10 years ago

Thank you for your feedback. However, I can't reproduce the segfault. Your file converts without problems on my system (tried with dvisvgm 1.0.5 and 1.0.7 on a Fedora system). Unfortunately, I don't have a Windows installation of TeX Live handy. If possible, please get a more recent version of dvisvgm and try again. If the problem still persists, I suggest to write to the TeX Live mailing list for further investigations.

Launchpad Details: #LPC Martin Gieseking - 2011-05-27 20:37:00 +0200

mgieseki commented 10 years ago

Your file converts without problems on my system (tried with dvisvgm 1.0.5 and 1.0.7 on a Fedora system). I also have no problem with this file and dvisvgm 1.0.6 under Debian.

If possible, please get a more recent version of dvisvgm and try again. I tried dvisvgm 1.0.8 from TeXLive 2011 and still have the bug.

I suggest to write to the TeX Live mailing list for further investigations. OK, I will try.

Launchpad Details: #LPC sfomin - 2011-06-02 19:47:00 +0200

mgieseki commented 10 years ago

I reproduce the bug on two different PC — both of them Windows 7, x64bit.

Also I made fresh install of TexLive-2010 (minimal+dvisvgm) — the bug still exists. I made small screencast http://vimeo.com/24614091

Launchpad Details: #LPC sfomin - 2011-06-03 16:35:00 +0200

mgieseki commented 10 years ago

OK, great. There seems to be an issue in the call of Metafont that doesn't occur on my test systems. In order to be able to isolate the problematic part of the code, could you please ask the TeX Live developers to build and send you a dvisvgm.exe with debug information enabled and code optimizations disabled? The stack trace of this executable would be of much more help. Without further information about the exact code location it's hard to find the origin of the segfault.

Launchpad Details: #LPC Martin Gieseking - 2011-06-03 18:07:00 +0200

mgieseki commented 10 years ago

Akira Kakuto has isolated the issue and sent a patch. I'm going to incorporate the changes in the next few days. Thank you again for reporting this issue, Stas.

Launchpad Details: #LPC Martin Gieseking - 2011-06-04 18:25:00 +0200

mgieseki commented 10 years ago

The bug has been fixed in the source repository (changeset fbf15e195038).

Launchpad Details: #LPC Martin Gieseking - 2011-06-05 07:51:00 +0200

mgieseki commented 10 years ago

The file bug.tex was added: minimal source tex file

Launchpad Details: #LPC sfomin - 2011-05-27 19:18:00 +0200

mgieseki commented 10 years ago

The file bug.dvi was added: DVI file (input to DVISVGM) caused crash.

Launchpad Details: #LPC sfomin - 2011-05-27 19:21:00 +0200