This is starting to sound like a 64-bit uncleanness issue. It probably has to do with the address where xpdf happens to be loaded in memory.
This is starting to sound like a 64-bit uncleanness issue. It probably has to
do with the address where xpdf happens to be loaded in memory.