<div dir="ltr"><div>If anyone is looking at pdfobj.c There is this assertion failure reported (with no reproducible example)</div><div><br></div><div><a href="https://tex.stackexchange.com/a/739668/1090">https://tex.stackexchange.com/a/739668/1090</a></div><div><br></div><div>David</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 4 Apr 2025 at 04:25, Shuqiao Zhang <<a href="mailto:stevenjoezhang@gmail.com">stevenjoezhang@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Karl,<div><br></div><div>Thank you for the response, and apologies — this was my first time reaching out via mailing list, and I’ll make sure to use the correct mailing list in the future.<br><br>The issue I encountered happened when using `\includegraphics` in TeX to import another PDF file. I’ve attached the related `.xdv` file and the PDF being included. (Note that the `.xdv` file may contain references to fonts included in the TeX Live 2025 environment, so it might require a full installation to reproduce the issue.)</div><div><br>The segmentation fault occurs during the following command executed by latexmk:<br><br> xdvipdfmx -q -E -o "build/main.pdf" "build/main.xdv"<br><br>Here is the version information:<br><br> $ latexmk --version<br> Latexmk, John Collins, 27 Dec. 2024. Version 4.86a<br> $ xdvipdfmx --version<br> This is xdvipdfmx Version 20250205 by the DVIPDFMx project team,<br> modified for TeX Live,<br> an extended version of DVIPDFMx, which in turn was<br> an extended version of dvipdfm-0.13.2c developed by Mark A. Wicks.<br> <br> Copyright (C) 2002-2025 the DVIPDFMx project team<br> Copyright (C) 2006-2025 SIL International.<br> <br> This is free software; you can redistribute it and/or modify<br> it under the terms of the GNU General Public License as published by<br> the Free Software Foundation; either version 2 of the License, or<br> (at your option) any later version.</div><div> $ uname -a<br> Linux epyc 6.8.0-56-generic #58-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 14 15:33:28 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux<br> $ lsb_release -a <br> No LSB modules are available.<br> Distributor ID: Ubuntu<br> Description: Ubuntu 24.04.2 LTS<br> Release: 24.04<br> Codename: noble<br></div><div><br>I hope this helps in reproducing the issue. For the functions related to the bug I discovered during debugging, please refer to the previous email.<br><br>Additionally, it seems that this problem is also influenced by heap memory layout, which means there's a chance that xdvipdfmx doesn't crash if the out-of-bounds pointer happens to fall on a valid memory page. I repeated to run the command 10 times (on Ubuntu 24.04), and in 8 of them, xdvipdfmx crashed. I also ran tests on other systems, using fresh installed TeX Live 2025: the crash also happens on macOS with Intel x86-64 architecture (macOS 13.6.6 22G630), but<span> </span>on macOS with Apple Silicon (macOS 15.3.2 24D81), xdvipdfmx works fine.</div><div><br>Best regards, </div><div><br>Shuqiao Zhang<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Karl Berry <<a href="mailto:karl@freefriends.org" target="_blank">karl@freefriends.org</a>> 于2025年4月4日周五 05:12写道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Shuqiao - thanks much for the report and patch. Please, please,<br>
provide the .xdv file that causes the crash. Otherwise we cannot verify<br>
it or make a test case.<br>
<br>
Also, for the future, (x)dvipdfm(x) reports are best sent to<br>
<a href="mailto:dvipdfmx@tug.org" target="_blank">dvipdfmx@tug.org</a>, not the general tex-live list. There's no need to<br>
resend this one, though.<br>
<br>
Thanks,<br>
Karl<br>
</blockquote></div>
</blockquote></div>