Update of bug #67978 (group groff):
Status: Confirmed => In Progress
Assigned to: None => gbranden
_______________________________________________________
Follow-up Comment #12:
Non-fuzzy reproducer:
$ cat ./ATTIC/67978alt3
.nr BarPos \n[.fp]
.sty \n[.fp] Bar
.fam Foo
.ft \n[BarPos]
.tm .f=\n[.f]
\X'baz'
$ groff --version | head -n 1
GNU groff version 1.24.0
$ groff ./ATTIC/67978alt3
troff:./ATTIC/67978alt3:3: error: no font family named 'Foo' exists
.f=41
groff: error: troff: Segmentation fault (core dumped)
The problem occurs because the `device_extension_node` class constructor
assumes that the current font mounting position is valid--meaning, there's an
"actual font" mounted there.
But that might not be the case: the current font mounting position might be an
abstract style.
It's somewhat difficult to get into that situation because all of the requests
and escape sequences for selecting fonts and styles go to some trouble to make
sure that the current mounting position is a "real" font, not an abstract
style.
But as the "Font Families" node of our Texinfo manual explains, it is possible
to manipulate oneself into a situation where the current mounting position
(tracked in register `.t`) is unavailable. I'd hyperlink to that, but because
today's weekday name ends in "y", www.gnu.org is timing out.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67978>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
