package groff-base
tag 421437 + upstream fixed-upstream
thanks
I can verify that, as I suspected (I mention that only because my
suspicions are so often incorrect), both instances arose from the same
bug, fixed in groff upstream last year and expected in the 1.23.0
release.
Details:
$ grodvi
Package: groff-base
Version: 1.18.1.1-12
Severity: normal
Running cat crash-grops.txt | grops /dev/null crashes grops with a
SIGSEGV. I know, I know, don't do that, but I'm writing a program which
outputs ditroff output suitable[0] for grops, and unfortunately, I'm
anticipating a lot of invalid
2 matches
Mail list logo