| Summary: | app-text/xpdf-3.02: crash on some files | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Eugene Zagidullin <e.asphyx> |
| Component: | Current packages | Assignee: | Printing Team <printing> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Stack backtrace
emerge --info Stack backtrace xpdf-3.92-poppler source package source package (updated) |
||
|
Description
Eugene Zagidullin
2007-11-20 21:23:54 UTC
Created attachment 136543 [details]
Stack backtrace
Created attachment 136545 [details]
emerge --info
Currently installed fontconfig-2.4.2, poppler-0.6.1-r1 Please, attach a more useful backtrace... http://www.gentoo.org/proj/en/qa/backtraces.xml Created attachment 136556 [details]
Stack backtrace
I have xpdf, poppler and fontconfig rebuilded with debugging info. More informative stack trace attached.
Much better indeed... :) hmh, thomas, do you have an idea why this is? How have you made that poppler version exactly? Is there any chance we could get this upstream to either poppler or xpdf? ;) (In reply to comment #7) > hmh, thomas, do you have an idea why this is? How have you made that poppler > version exactly? Is there any chance we could get this upstream to either > poppler or xpdf? ;) > Hard to tell, either this is a mere poppler problem, because if you do a: $ pdf2ps yourpdffile.pdf $ ps2pdf yourpdffile.ps the resulting pdf will work. (both are poppler command line tools.) Or it is indeed the conflict of the redundant code in xpdf, the GlobalParams.* are right now included in the xpdf-3.02-poppler package, even though they are also provided by poppler (some functions are missing there though) In poppler uses fcfg slightly differently in their constructor, compared to xpdf. I will try to compile xpdf with the patched poppler and see if the problem remains. Ok, with the patched poppler version it works correct. So it seems xpdf doesn't initialize some Fontconfig stuff, that poppler later wants to access, so basically we need to patch poppler, I will try to get the patch upstream, again. regards, Thomas Created attachment 136636 [details]
xpdf-3.92-poppler source package
Poppler doesn't really want to include xpdf specific stuff it seems, they provide the xpdf headers only per flag, anyhow, this package should fix the breakage for now
Created attachment 136638 [details]
source package (updated)
sorry, I forgot to clean the package, before uploading it :p
I wonder, how have you fixed it now? Anyway, thanks for fixing. Well, instead of patching poppler with the xpdf code, I patched xpdf with the poppler code :p This solution is also sub-optimal though, but it should do the trick now. I hope no other bug will emerge, and I will keep trying to get the xpdf patch for poppler upstream, but xpdf never was supposed to be spereated in library style, so it is kind of a compromise for the poppler guys whether to include xpdf code or not. regards, Thomas |
