Dvips fails in texlive 2022, texlive 2023 and MacTeX

Bruno Voisin bvoisin at icloud.com
Tue Jul 25 20:21:38 CEST 2023

This comes late, but just in case:

On a Mac with MacTeX 2023,

(1) LaTeXing your example test.tex with TeXShop in TeX and Dvi mode (all fine, PDF output is produced by tex + dvips + ps2pdf as it should),

(2) applying "dvips -d -1 test.dvi > test-log.txt 2>&1", and

(3) comparing this test-log.txt and your dvips_test_a.txt with BBEdit,

it appears you have a /usr/local/texlive/texmf-local/dvips/local/config.ps with content

	%   Main config file for dvips5.86
	%   With a virtual machine, we can claim 1M of memory.
	m 1000000
	%   Default resolution. (600 dpi postscript printer)
	D 300
	M CanonCX
	%   Uncomment this line to enable hyperdvi to hyperpostscript conversion
	%   Uncomment this line to disable partial font downloading.
	%   Uncomment this line to have dvips shift lower characters to a higher position.
	%   Load in various Postscript mapping files. Psfonts.map is always read.
	p +adobe-lwfn.map

This file is read instead of /usr/local/texlive/2023/texmf-config/dvips/config/config.ps. Among other things, it

- changes the available memory (compared with the default 3500000),

- causes dvips to read /usr/local/texlive/texmf-local/fonts/map/dvips/adobe-lwfn.map (as noticed by Alois Steindl) instead of /usr/local/texlive/2023/texmf-var/fonts/map/dvips/updmap/psfonts.map.

I leave it to the experts here to determine the effects this may have. The template config.ps you seem to have used was for dvips 5.86, pre-TeX Live 2010, the current version is 2023.2.

Just one thing: despite the "+" in your "p +adobe-lwfn.map", based on your debug output, it seems the global psfonts.map is not read at all, only your local adobe-lwfn.map is read.

Maybe dvips tries to read adobe-lwfn.map first, this causes the buffer overflow you report and dvips crashes?

Hope this helps,

Bruno Voisin

More information about the tex-live mailing list.