With rc3: Program received signal SIGSEGV, Segmentation fault. 0x80a64c5 in lookup_fontmap (bname=0x830c180 "LUTYFL+CMBX12") at ../../../../src/texk/web2c/pdftexdir/mapfile.c:755 755 if (pdffontmap[i] == 0) (gdb) bt #0 0x80a64c5 in lookup_fontmap (bname=0x830c180 "LUTYFL+CMBX12") at ../../../../src/texk/web2c/pdftexdir/mapfile.c:755 #1 0x80b6723 in copyFont (tag=0x830cee0 "F128", fontRef=0xbfffce20) at ../../../../src/texk/web2c/pdftexdir/pdftoepdf.cc:425 #2 0x80b6cfc in copyFontResources (obj=0xbfffcf04) at ../../../../src/texk/web2c/pdftexdir/pdftoepdf.cc:458 #3 0x80b892d in write_epdf () at ../../../../src/texk/web2c/pdftexdir/pdftoepdf.cc:1004 #4 0x80b54f5 in writeimage (img=0) at ../../../../src/texk/web2c/pdftexdir/writeimg.c:316 #5 0x807c9fc in zpdfwriteimage (n=6) at pdftex1.c:7324 #6 0x809b653 in doextension () at pdftex3.c:792 #7 0x809e355 in maincontrol () at pdftex3.c:2283 #8 0x805a150 in mainbody () at pdftexini.c:4908 #9 0x80a1bbe in main (ac=4, av=0xbfffd094) at pdftexextra.c:325 Will investigate further tomorrow. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
Hi Martin, can you please send me a minimal set of test files to reproduce the bug? Thanks, Thanh On Tue, May 11, 2004 at 05:05:46PM +0200, Martin Schroeder wrote:
With rc3:
Program received signal SIGSEGV, Segmentation fault. 0x80a64c5 in lookup_fontmap (bname=0x830c180 "LUTYFL+CMBX12") at ../../../../src/texk/web2c/pdftexdir/mapfile.c:755 755 if (pdffontmap[i] == 0) (gdb) bt #0 0x80a64c5 in lookup_fontmap (bname=0x830c180 "LUTYFL+CMBX12") at ../../../../src/texk/web2c/pdftexdir/mapfile.c:755 #1 0x80b6723 in copyFont (tag=0x830cee0 "F128", fontRef=0xbfffce20) at ../../../../src/texk/web2c/pdftexdir/pdftoepdf.cc:425 #2 0x80b6cfc in copyFontResources (obj=0xbfffcf04) at ../../../../src/texk/web2c/pdftexdir/pdftoepdf.cc:458 #3 0x80b892d in write_epdf () at ../../../../src/texk/web2c/pdftexdir/pdftoepdf.cc:1004 #4 0x80b54f5 in writeimage (img=0) at ../../../../src/texk/web2c/pdftexdir/writeimg.c:316 #5 0x807c9fc in zpdfwriteimage (n=6) at pdftex1.c:7324 #6 0x809b653 in doextension () at pdftex3.c:792 #7 0x809e355 in maincontrol () at pdftex3.c:2283 #8 0x805a150 in mainbody () at pdftexini.c:4908 #9 0x80a1bbe in main (ac=4, av=0xbfffd094) at pdftexextra.c:325
Will investigate further tomorrow.
Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de _______________________________________________ ntg-pdftex mailing list ntg-pdftex@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-pdftex
Hi, I found the bug. Before fixing it, I would like to discuss more about the behaviour of lookup_fontmap(). For a given base name there may exist several map lines containing that name. The question is which of them should be returned? At the moment the first one with matching extent and slant is returned. I wonder whether we can narrow this criteria to something more strict. For example, we can choose which tfm should be used regard to the following checks (in descending priority): * the tfm has been used (some char from this font has been typeset) * the tfm has been loaded (but not used yet) * the tfm can be loaded (but not loaded yet) * the tfm is present in map files, but cannot be loaded. In this case a dummy tfm can be loaded instead, and warning should be written Please let me know your opinion. Thanh
On 2004-05-12 16:22:46 +0700, The Thanh Han wrote:
* the tfm has been used (some char from this font has been typeset) * the tfm has been loaded (but not used yet) * the tfm can be loaded (but not loaded yet) * the tfm is present in map files, but cannot be loaded. In this case a dummy tfm can be loaded instead, and warning should be written
Seems o.k. to me. Best regards Martin -- Martin Schröder, ms@artcom-gmbh.de ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10 http://www.artcom-gmbh.de
At 11:22 12/05/2004, The Thanh Han wrote:
At the moment the first one with matching extent and slant is returned.
i'd like the last one to be returned, since later definitions may override previous ones; (\pdfmapfile, \pdfmapline provide more control, and there's also the +-= prefixing that hartmut implemented; i hope that this will not get lost)
I wonder whether we can narrow this criteria to something more strict. For example, we can choose which tfm should be used regard to the following checks (in descending priority):
* the tfm has been used (some char from this font has been typeset) * the tfm has been loaded (but not used yet) * the tfm can be loaded (but not loaded yet) * the tfm is present in map files, but cannot be loaded. In this case a dummy tfm can be loaded instead, and warning should be written
what is the purpose of that dummy tfm file? Hans
I wonder whether we can narrow this criteria to something more strict. For example, we can choose which tfm should be used regard to the following checks (in descending priority):
* the tfm has been used (some char from this font has been typeset) * the tfm has been loaded (but not used yet) * the tfm can be loaded (but not loaded yet) * the tfm is present in map files, but cannot be loaded. In this case a dummy tfm can be loaded instead, and warning should be written
what is the purpose of that dummy tfm file?
this is for handling font files in embedded pdf files. Thanh
participants (4)
-
Hans Hagen -
Martin Schröder -
The Thanh Han -
Tom Kacvinsky