[tlbuild] dvi test?

[John Hawkinson]

Multiple replies in-line below.

Mojca Miklavec <mojca.miklavec.lists at gmail.com> wrote on Mon, 24 Jan 2022
at 01:08:57 EST in <CALBOmsagm+p9D65RzDhwUwEczSzsXuvmbzTh9Pz1c1mVT0ANrw at mail.gmail.com>:

> I'm not saying it's the case here, but if it works with the TL 2015
> binaries (which were probably still compiled against libstdc++) and
> fails now, this could be a possible explanation.

Hi. Just to be clear, the TL 2015 binaries do *not* avoid the crash.

Or rather, the TL2015 binaries do not crash on my old machine, running xdvik version 22.87, XQuartz 2.7.11, MacOS Sierra 10.12.6).

But when those same x86_64 TL2015 binaries are run on the arm64 machine (under emulation) with the newer OS and newer X11 environment, they break in exactly the same way as the native arm64 Tl2021 binaries do.


Paul Vojta <vojta at math.berkeley.edu> wrote on Mon, 24 Jan 2022
at 01:15:43 EST in <Ye5EDyH8jxNxQ9ti at math.berkeley.edu>:

> In a separate thread (not on any mailing lists that I could see),
> Richard Koch pointed to the (old) bug
> 
> 	https://bugs.freedesktop.org/show_bug.cgi?id=96292
> 
> and people seemed to agree that this was it.

Err, Richard raised that on the tex-live list, https://tug.org/pipermail/tex-live/2022-January/047686.html

But I don't think anyone agreed that was the source of my xdvik problems. I don't see any reason to think it would be, that was a crash in X11 code resulting from mismatched dynamic libraries. There's nothing like that in the xdvik stack trace that I get from this problem.

I'd be greatful if anyone has suggestions for what to instrument, trace, or breakpoint on while debugging xdvi, as I have a working build tree and functional debugger now.

--
jhawk at alum.mit.edu
John Hawkinson