Peter Fales schrieb: > Now that's wierd. I was using a privately built copy of unpaper, but I > just unpacked the tarball and get the same results with the prebuilt binary!
I just reproduced the problem on one remote Intel machine I have access to. Try to compile without any optimization (no -Ox), this was the only way for me to get a usable executable for that machine. Does it help for you? (I am using gcc 3.3.5 on Debian.) Jens > > It seems that the same demo file and binary works for you but gives a white > page for me. I can't think of any reason why that would be. My first > thought was shared libraries, but unpaper doesn't seem to have any unusual > shared library dependencies. Do you invoke any external programs that > might be different on my system? > > I'll try to take a look at the code this weekend and see if I see any ideas. > If you have any debugging you want me to do (e.g. strategically placed > printf's ) just let me know. >
