Bugs item #250, was opened at 2004-12-11 19:15 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=250&group_id=106 Category: Fonts Group: v1.20a
Status: Closed Resolution: Fixed Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Hartmut Henkel (hhenkel) Summary: writet1.c has problems with HUGE fonts. Patch.
Initial Comment: Font GoudyIn.pfb causes pdftex segfault, see the README coming with the patch. This tries a fix by dynamic allocation of buffers. As a by-result, PFB and PFA font embedding speed seems to be increased. Needs more testing... ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2004-12-22 15:53 Message: Logged In: YES user_id=421 This has been fixed in 1.20b ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2004-12-12 10:00 Message: Logged In: YES user_id=929 Tried to force re-allocations and made tests with pdftex and dvipsk, see attached .tgz file. Seems to run ok. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2004-12-11 19:39 Message: Logged In: YES user_id=1608 My version pdfxtex did not exactly segfault, instead it gave the following pdftex_warning(): CharString: invalid access (1) to stack (0 entries) (and gdb showed a somewhat corrupt backtrace, probably both a symptom of the wild pointer). The patch fixed the problem, and I am now looking at a correct PDF document. And I also think it is somewhat faster than before. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=250&group_id=106