Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InvalidDVIFileException in upTeX DVI only on Solaris #261

Open
t-tk opened this issue Jan 28, 2024 · 2 comments
Open

InvalidDVIFileException in upTeX DVI only on Solaris #261

t-tk opened this issue Jan 28, 2024 · 2 comments
Assignees

Comments

@t-tk
Copy link

t-tk commented Jan 28, 2024

I wrote a test of dvisvgm for upTeX DVI and I have gotten core dump only on Solaris environments.
If you have any idea to fix it, I'm glad to have your advise.

https://build.contextgarden.net/#/console
texlive.solaris-i386.csw
texlive.solaris-sparc.csw
texlive.solaris-x86_64.csw

From the log of Build/source/texk/dvisvgm/tests/dvisvgm-uptex.test

+ ./dvisvgm-src/src/dvisvgm --verbosity=7 -m upjf.map -o upjf1_full.svg ../../../texk/dvisvgm/tests/upjf.dvi 
pre-processing DVI file (format version 3)
WARNING: no font file found for 'upjv-r'
WARNING: no font file found for 'upjv-g'
WARNING: no font file found for 'upjf-r'
WARNING: no font file found for 'upjf-g'
processing page 1
terminate called after throwing an instance of 'InvalidDVIFileException'
  what():  invalid DVI file
Abort - core dumped
@mgieseki
Copy link
Owner

Unfortunately, I have no idea. The logs contain too little information to determine the cause of the exception. I don't have access to a Solaris system either, so I can't debug this issue.

@mgieseki
Copy link
Owner

I tried to investigate this a little further but without much success. Since the exception leads to a core dump which should not happen (because all exceptions get caught in the code), I suppose this is a bug in GCC 5.5. Thus, I suggest to test it again with a newer version if possible.

The warning messages are related to the map file that probably doesn't contain information on the font files assigned to the mentioned font names.

@mgieseki mgieseki self-assigned this Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants