xdvipdfmx segfault

Vít Starý Novotný witiko at gmail.com
Tue Mar 5 14:30:32 CET 2024


Dear all,

I can add another test case for the segfault.

Since at least two days ago, the Markdown package [has failed to compile
XeLaTeX example document][1] with TeX Live pretest due to a segmentation
fault with AMD64 binaries for Linux:


- [Compilation logs from 2024-02-28][4] (success)

- [Compilation logs from 2024-03-03][2] (failure)

- [Compilation logs from 2024-03-05][3] (failure)


[1]: https://github.com/Witiko/markdown/actions

[2]:
https://github.com/Witiko/markdown/actions/runs/8127770761/job/22212974098

[3]:
https://github.com/Witiko/markdown/actions/runs/8151062393/job/22278370166

[4]: https://github.com/Witiko/markdown/actions/runs/8075304001


I was able to create an MWE that reproduces the issue with current TeX Live
pretest:


```

$ xelatex example

This is XeTeX, Version 3.141592653-2.6-0.999996 (TeX Live 2024) (preloaded
format=xelatex)

\write18 enabled.

entering extended mode

(./latex-xetex.tex

LaTeX2e <2023-11-01> patch level 1

L3 programming layer <2024-02-20>

[... snip]

[7] [8] [9] (./_markdown_example/89a89e0981b83735997c42f3f5d93a6b.verbatim)

(./_markdown_example/07fe0bf180fb395d67966e3c3b0b3177.verbatim) [10] [11]

(./example.aux) )

Segmentation fault (core dumped)

(see the transcript file for additional information)

Error 35584 (driver return code) generating output;

file example.pdf may not be valid.

Transcript written on example.log.

```


You will find an archive with the MWE attached.


Best,

Vít Starý Novotný

On Tue, Mar 5, 2024 at 1:28 PM Pablo González L <pablgonz at educarchile.cl>
wrote:

> > With a fully updated TL2024 pretest I can confirm that
> >
> >  \documentclass{article}
> >   \usepackage{graphicx}
> >   \begin{document}
> >       \includegraphics{example-image.pdf}
> >
> >       \includegraphics{example-image.pdf}
> >   \end{document}
> >
> > fails when typeset with xelatex but typesets fine with pdflatex and
> lualatex.
> >
> Under fedora linux 39 I get (TL24 updated as of today)
> Error 139 (driver return code) generating output;
> file test.pdf may not be valid.
> Transcript written on test.log.
>
> But under windows 11 (TL24 updated as of today) it compiles without
> problems.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/tex-live/attachments/20240305/800ca584/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.zip
Type: application/zip
Size: 3885 bytes
Desc: not available
URL: <https://tug.org/pipermail/tex-live/attachments/20240305/800ca584/attachment.zip>


More information about the tex-live mailing list.