Bugs item #2487687, was opened at 2009-01-05 15:34 Message generated for change (Comment added) made by prokoudine You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=790130&aid=2487687&group_id=154028
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: podofoimpose segfault ibn scribus's PDFs Initial Comment: podofoimpose (0.7.0) segfaults on Scribus 1.3.5 PDF files with embedded fonts (e.g. DejaVu Serif). GDB backtrace is attached. Any test file from 1.3.5 (didn't try stable) will work. Confirmed by another user. ---------------------------------------------------------------------- Comment By: Alexandre Prokoudine (prokoudine) Date: 2009-01-06 22:09 Message: Craig, it's tens of thousands of migrateResource() fails, not hundreds. In fact I had to power off my laptop because gdb just froze X session. I will attach PDF file asap. ---------------------------------------------------------------------- Comment By: Craig Ringer (ringerc) Date: 2009-01-05 17:53 Message: That's odd. It looks almost like it could be an out-of-memory condition, but usually that'd result in a SIGABRT (signal 6) not a SIGSEGV. Your libc isn't debug enabled, nor is your build of PoDoFo or libstdc++, so it's a bit hard to tell exactly what's going on; I can really only see that it's crashing while converting a PDFReference to its string representation, in the process of which it's having to expand a std::string, trying, and failing during memory allocation. This could be due to memory exhaustion, a stack overflow, or of course something else entirely. Since a PDFReference is of the fixed form "[integer] [integer] R", memory exhaustion is presumably not the immediate problem. We won't be allocating vast amounts of memory for that. So it must be in some kind of infinite or at least very deep loop where it's creating lots of objects and not releasing them - or where the depth of the call stack is its self the problem. That's presumably an issue in migrateResource(). Your backtrace is incomplete - are there LOTS of calls (hundreds?) to migrateResource() by any chance? It'd be helpful if you could attach a PDF just so we're all talking about the same file when looking at this. I don't have Scribus 1.3.5 at present and would rather have something I know crashes for you anyway. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=790130&aid=2487687&group_id=154028 ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Podofo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/podofo-users
