I haven't heard of this before. I'm sure this is easy to diagnose for someone who can reproduce it. I can't, since I don't have access to a system other than AMD64.
I can tell from reading the code that what is happening is there is a a negative number somewhere that there shouldn't be. My best guess is that the 2's complement arithmetic hack for interpreting the run-length-encoding in the function 'readPackBitsRow16' in converter/other/pnmtopalm/palmtopnm.c isn't doing what it's expected to do. In particular, the line int const signedIncount = (signed char)incountByte might be declaring a positive number, whereas it's supposed to be negative (which means -signedIncount below is negative whereas it is expected to be positive). -- Bryan Henderson San Jose, California