<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - pdftops generated postscript has missing letters (in 64bit processor)" href="https://bugs.freedesktop.org/show_bug.cgi?id=71038#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - pdftops generated postscript has missing letters (in 64bit processor)" href="https://bugs.freedesktop.org/show_bug.cgi?id=71038">bug 71038</a> from <a class="email" href="mailto:ingenieria@binariadigital.com" title="Binaria <ingenieria@binariadigital.com>"> Binaria</a> <pre>(In reply to <a href="show_bug.cgi?id=71038#c13">comment #13</a>) > does running pdftops under valgrind give you any warning? Hi again, here is valgrind output for our CentOS 64bits machine. (trimmed out unimportant lines) valgrind pdftops testFile2.pdf: ==16029== ==16029== HEAP SUMMARY: ==16029== in use at exit: 68,754 bytes in 868 blocks ==16029== total heap usage: 27,187 allocs, 26,319 frees, 248,213,759 bytes allocated ==16029== ==16029== LEAK SUMMARY: ==16029== definitely lost: 0 bytes in 0 blocks ==16029== indirectly lost: 0 bytes in 0 blocks ==16029== possibly lost: 0 bytes in 0 blocks ==16029== still reachable: 68,754 bytes in 868 blocks ==16029== suppressed: 0 bytes in 0 blocks ==16029== Rerun with --leak-check=full to see details of leaked memory ==16029== ==16029== For counts of detected and suppressed errors, rerun with: -v ==16029== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6) valgrind --tool=helgrind ==17953== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) valgrind --tool=drd ==22923== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Trying to get an unified testing enviroment i have also tried vagrant+virtual box running this image (CentOS 6.5 64bit): <a href="https://github.com/2creatives/vagrant-centos/releases/download/v0.1.0/centos64-x86_64-20131030.box">https://github.com/2creatives/vagrant-centos/releases/download/v0.1.0/centos64-x86_64-20131030.box</a> minimal setup for vagrant just name of the box+url all the rest default options. I ran it in Centos 32bits as host OS. (in this machine pdftops outputs correct ps files.) Inside Centos 6.5 VM just: yum install poppler-utils (v 0.12.4 in repo) pdftops /pathTo/testFile2.pdf /pathTo/testFile2.ps -> missing letters in this testFile2.ps file again. (as viewed with evince) This way you can test in the "same" environment. Inside VM valgrind outputs the same: [vagrant@vagrant-centos65 ~]$ valgrind --leak-check=yes pdftops /vagrant/Descargas/testFile2.pdf ==7699== Memcheck, a memory error detector ==7699== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==7699== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==7699== Command: pdftops /vagrant/Descargas/testFile2.pdf ==7699== ==7699== ==7699== HEAP SUMMARY: ==7699== in use at exit: 55,370 bytes in 709 blocks ==7699== total heap usage: 26,720 allocs, 26,011 frees, 247,867,541 bytes allocated ==7699== ==7699== LEAK SUMMARY: ==7699== definitely lost: 0 bytes in 0 blocks ==7699== indirectly lost: 0 bytes in 0 blocks ==7699== possibly lost: 0 bytes in 0 blocks ==7699== still reachable: 55,370 bytes in 709 blocks ==7699== suppressed: 0 bytes in 0 blocks ==7699== Reachable blocks (those to which a pointer was found) are not shown. ==7699== To see them, rerun with: --leak-check=full --show-reachable=yes ==7699== ==7699== For counts of detected and suppressed errors, rerun with: -v ==7699== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6) [vagrant@vagrant-centos65 ~]$ valgrind --tool=drd pdftops /vagrant/Descargas/testFile2.pdf ==1463== drd, a thread error detector ==1463== Copyright (C) 2006-2012, and GNU GPL'd, by Bart Van Assche. ==1463== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==1463== Command: pdftops /vagrant/Descargas/testFile2.pdf ==1463== ==1463== ==1463== For counts of detected and suppressed errors, rerun with: -v ==1463== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) etc...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>