Bug#398354: tetex-bin: pdflatex segfaults
clone 398354 -1
retitle -1 Should not use xpdf configuration files
thanks
Dear poppler people,
Gabor Gombas <gombasg@sztaki.hu> wrote:
> pdflatex dies with "Segmentation fault" when called by the pdfnup
> utility; the last part of the strace output looks like:
Let's forget for a while (and in this clone of the bug) that it
shouldn't segfault and just inspect the strace output:
> open("/etc/xpdf/xpdfrc-latin2", O_RDONLY|O_LARGEFILE) = 8
> fstat64(8, {st_mode=S_IFREG|0644, st_size=143, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6b50000
> read(8, "#----- begin Latin2 support pack"..., 4096) = 143
> read(8, "", 4096) = 0
> close(8) = 0
> munmap(0xb6b50000, 4096) = 0
> open("/etc/xpdf/xpdfrc-thai", O_RDONLY|O_LARGEFILE) = 8
> fstat64(8, {st_mode=S_IFREG|0644, st_size=196, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6b50000
> read(8, "#----- begin Thai support packag"..., 4096) = 196
> open("/usr/share/xpdf/thai/Thai.nameToUnicode", O_RDONLY|O_LARGEFILE) = 9
I'm surprised that an application that is dynamically linked against
libpoppler reads xpdf configuration files and even files in /usr/share.
If this is intended, it should be documented clearly. But in fact it
seems to me that it would be better to fork the names of these files,
too.
> ii libpoppler0c2 0.5.0-1 PDF rendering library
Is this a known issue?
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
Reply to: