[tex4ht] [bug #611] Random SIGSEGV of tex4ht due to invalid memory accesses

Oliver Freyermuth puszcza-hackers at gnu.org.ua
Sat Oct 14 23:33:57 CEST 2023

Follow-up Comment #5, bug #611 (project tex4ht):

Hi again Karl,

many thanks! I don't see any problem with the memset call, and can confirm
this also makes valgrind blissfully silent on my end when applying the patches
to tex4ht on my local desktop (Gentoo Linux). I tested with various documents
and various parameters and found no problems. 

Since Gentoo currently seems to package an old snapshot of tex4ht based on a
not-directly-upstream source, I have pinged the corresponding maintainer to
pull in the fixes or ideally just switch to upstream ( for reference:
https://bugs.gentoo.org/915782 ). 

In my CI/CD pipeline which I am running via GitHub actions to produce HTML
pages for deployment with GitHub pages, I am actually relying on Docker
containers based on Alpine Linux with Texlive binaries installed via tlmgr.
Hence, that would be x86_64-linuxmusl binaries. In case those are easy for you
to build, of course that would be appreciated, if not, waiting for TL24 is
also fine for me (it's not that far off, and knowing the issue is fixed for
good makes me very happy :-) ). 

Cheers and many thanks for fixing things so quickly! 


Reply to this item at:


  Message sent via/by Puszcza

More information about the tex4ht mailing list.