On Wed, 01 Nov 2017 15:04:43 +0100 Johannes Schauer <jo...@debian.org> wrote: > The problem is, that executing pdf2htmlEX results in a segmentation fault. > Here > is a backtrace: > > #0 0x00007ffff7442a9f in NOUI_SavePrefs (not_if_script=<optimized out>) at > ././fontforge/noprefs.c:859 > #1 0x00007ffff7441fb3 in NOUI_SetPrefs (name=0x55555559d772 > "DetectDiagonalStems", val1=0x7fffffffe850, val2=0x0) at > ././fontforge/noprefs.c:431 > #2 0x000055555558f7de in ffw_init (debug=0) at ./src/util/ffw.c:77 > #3 0x000055555557fae2 in > pdf2htmlEX::HTMLRenderer::HTMLRenderer(pdf2htmlEX::Param const&) > (this=0x555555809660, param=...) at ./src/HTMLRenderer/general.cc:58 > #4 0x000055555556cdc4 in main(int, char**) (argc=<optimized out>, > argv=<optimized out>) at ./src/pdf2htmlEX.cc:421 > > So the problem is indeed serious but the segmentation fault seems to happen in > fontforge.
The problem is: (gdb) p *((Encoding **) (pl->val)) $9 = (Encoding *) 0x55859a00 (gdb) p (*((Encoding **) (pl->val)))->enc_name Cannot access memory at address 0x55859a00 I don't know enough about fontforge to fix this problem and fontforge upstream doesn't seem to have time for the software anymore: http://pdf2htmlex.blogspot.de/2016/12/looking-for-new-maintainer.html https://github.com/coolwanglu/pdf2htmlEX/issues/726 If this situation doesn't improve, then I guess it's best to not have this package in Buster anyways...
signature.asc
Description: signature
