Created attachment 67176 [details] PDF test case This was reported in GNOME Bugzilla (evince), however, this bug belong to poppler. I can reproduce it with poppler-glib-demo, when it renders the pdf. I tried with master (b72c02d1a2e), from Sep 13, 2012. Here is the origina report: This file was generated by mathematica 8.0.4, and when I view it directly with evince or embed it in a LaTeX PDF and view that, I get error messages on the console Error (220): Arg #0 to 'm' operator is wrong type ((null)) Error (223): Arg #0 to 'l' operator is wrong type ((null)) Error (225): No current point in lineto Error (227): Arg #1 to 'l' operator is wrong type ((null)) Error (252): Arg #0 to 'm' operator is wrong type ((null)) Error (252): Arg #0 to 'l' operator is wrong type ((null)) Error (252): No current point in lineto etc. I don't know whether the PDF is malformed or if there's some corner case that evince doesn't cover or what. Mathematica does sometimes create strange files with things like infinite rectangles for the background. The problem seems to be mostly harmless-- the picture looks okay on the screen and in print. But I thought I should report it.
This is indeed a real bug in the Lexer that is not able to parse correctly the -2147483648 number. I have a patch but want to give it some more test, will probably commit it tomorrow
Fixed
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.