FS#60526 - [mupdf-tools] Segmentation fault (core dumped) during `mutool convert`

Attached to Project: Community Packages
Opened by BH (braderhart) - Monday, 22 October 2018, 08:50 GMT
Last edited by Toolybird (Toolybird) - Monday, 17 April 2023, 07:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


# Description:

I am getting a "Segmentation fault (core dumped)" while trying to convert using `mutool`

Additional info:
* package version: 1.14.0-1

Steps to reproduce:

`mutool convert -o test.pdf image.pnm`
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 17 April 2023, 07:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  Cannot repro. Seems to have been fixed.
Comment by Gaetan Bisson (vesath) - Monday, 22 October 2018, 18:24 GMT
Here's another test case to reproduce this problem. The file `d.pdf` can be obtained by running `pdflatex d.tex`.

Then, running `mutool convert -o o.pdf d.pdf` yields a segmentation fault. The backtrace is not very enlightening:

Starting program: /usr/bin/mutool convert -o o.pdf d.pdf
Program received signal SIGSEGV, Segmentation fault.
0x000055555560cb2a in ?? ()
(gdb) bt
#0 0x000055555560cb2a in ?? ()
#1 0x00005555555b068a in ?? ()
#2 0x00005555556372a4 in ?? ()
#3 0x00005555556373d3 in ?? ()
#4 0x0000555555626385 in ?? ()
#5 0x000055555558e63a in ?? ()
#6 0x000055555558e722 in ?? ()
#7 0x000055555558eac8 in ?? ()
#8 0x00007ffff72ca223 in __libc_start_main () from /usr/lib/libc.so.6
#9 0x000055555558e35e in ?? ()
   d.pdf (10.7 KiB)
   d.tex (0.1 KiB)
Comment by Gaetan Bisson (vesath) - Monday, 22 October 2018, 18:28 GMT
Building the latest mupdf git snapshot with `make debug` results in a mutool binary that does not segfault on the above arguments but produces an empty-looking output file `o.pdf`.