pdflatex does not work on win after todays update but does on linux
Siep Kroonenberg
siepo at bitmuis.nl
Sun Jun 13 10:49:39 CEST 2021
On Sat, Jun 12, 2021 at 10:22:56PM +0200, Andreas Hirsch wrote:
> Hi Siep,
>
> Siep Kroonenberg schrieb am 12.06.2021 um 15:09:
>
> > With me, the last line of output with KPATHSEA_DEBUG=-1 is:
> >
> > kdebug:fsyscp_xfopen(192.168.101.1/tldev/Master/texmf-var/web2c/pdftex/pdflatex.fmt [], rb) => 0x6f6a3068
> >
> > > Does it always crash at the same place? If a document depends on many
> > > packages, does pdflatex --recorder always generate the same .fls file?
> >
> > PWD x:/textest/lin_regression
> > INPUT //192.168.101.1/tldev/Master/texmf.cnf
> > INPUT //192.168.101.1/tldev/Master/texmf-dist/web2c/texmf.cnf
> > INPUT //192.168.101.1/tldev/Master/texmf-var/web2c/pdftex/pdflatex.fmt
> >
> > gdb --args pdflatex lin_regression
> >
> > Reading symbols from pdflatex...(no debugging symbols found)...done.
> > (gdb) r
> > Starting program: \\192.168.101.1\tldev\Master\bin\win32\pdflatex.exe lin_regression
> > [New Thread 4776.0x330]
> > [New Thread 4776.0x21c]
> > [New Thread 4776.0x5dc]
> > This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2021/W32TeX) (preloaded format=pdflatex)
> > restricted \write18 enabled.
> >
> > Thread 1 received signal SIGSEGV, Segmentation fault.
> > 0x6f751780 in pdftex!dllpdftexmain ()
> > from \\192.168.101.1\tldev\Master\bin\win32\pdftex.dll
> >
> > (gdb) bt
> > #0 0x6f751780 in pdftex!dllpdftexmain ()
> > from \\192.168.101.1\tldev\Master\bin\win32\pdftex.dll
> >
> > I have also been piddling around with the utilities from
> > sysinternals.com, in particular procmon / process monitor. But it
> > gives you a deluge of data in which you have to search for the
> > relevant stuff.
>
> same for me - I'm not able to extract the relevant information
>
> As I wrote in previous mail, the problem occured at two different Windows 10
> machines (20H2 versus 21H1), different manufacturer and nothing has been
> changed than a TeXLive-Update BUT the error occurred at the same time
>
> I would regard it helpful if we can determine that the combination of
>
> Win 10 + pdflatex (pdftex.dll) + LaTeX 2021-06-01
>
> is not the culprit.
>
> Maybe it is only the culprit if the installation is on an network-share?
No problem with a local installation.
On w7 and w8 I ran into the same problem as on w10 with a samba
installation. Apparently, it is the network installation, not the
windows version.
--
Siep Kroonenberg
More information about the tex-live
mailing list.