Re: To bust or not to bust: the C/C++ code freeze for a (poor man's) fuzzer-provoked SEGV

On Wednesday, 28 January 2026 22:27:09 GMT G. Branden Robinson wrote:
> 	Show Details
> Hi Deri,
> 
> [somewhat rearranged]
> 
> At 2026-01-28T20:49:25+0000, Deri wrote:
> > I agree with Bruno, the fix can wait. I'm not sure about this one
> > though,
> > 
> > [derij@pip build (master)]$ echo "\X'pdf: xrev'"|groff -Tpdf -ms -Z
> > x T pdf
> > x res 72000 1 1
> > x init
> > p1
> > troff: src/roff/troff/input.cpp:3107: const char*
> > token::description(): Assertion `0 == "unhandled case of `type`
> > (token)"' failed.
> > groff: error: troff: Aborted (core dumped)
> 
> Good catch--I wasn't aware of this.
> 
> > it seems to be only in current groff:-

I only discovered it when doing the research for the pdf attached to <https://
savannah.gnu.org/bugs/?67544#comment8>. I wanted to attach a .png at the top 
of the page:-

.LP
\X'pdf: pdfpic ne-pic.png -L \n[LL]z'
.sp 1.4c
.NH 1 ghostscript
Ghostscript

It only avoided the SIGSEGV if I added a .LP before it.

Cheers

Deri