- ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] Fwd: Rebuilding pdftex gives ---! Must increase the hyph_size (Fatal format file error; I'm stymied)
by Thanh Han The 27 Aug '08

27 Aug '08

pdftex (and any program that uses kpathsea) can be run from any location, but one has to set TEXMFCNF to the right location (and probably edit texmf.cnf slightly). Personally I use TEXMFCNF=/opt/texlive/texmf-config/web2c:/opt/texlive/texmf-main/web2c where /opt/texlive/texmf-main/web2c/texmf.cnf is the original texlive texmf.cnf, and I put my changes /opt/texlive/texmf-config/web2c/texmf.cnf to override a few tl settings. Thanh On Tue, Aug 26, 2008 at 03:31:46PM +0300, Vasile Gaburici wrote: > Thanks, the patch is not the problem. The problem is that one cannot > run pdftex from the build dir. It needs to sit in a TDS to be able to > find the config files plus all the tex stuff required to build the fmt > file. In my case it could not find texmf.cnf at all, so it used some > defaults, hence the error. > > On Tue, Aug 26, 2008 at 3:15 PM, Thanh Han The <hanthethanh(a)gmail.com> wrote: > > you can try to compile pdftex from sources, but without your > > patch. > > > > 1. if it works, then the problem is likely with the patch. > > > > 2. if not, the problem is likely with your tex config. > > > > > > Thanh > > > > On Tue, Aug 26, 2008 at 02:34:45PM +0300, Vasile Gaburici wrote: > >> I'm not sure that anyone reads pdftex(a)tug.org, so I'm trying my luck > >> on this list: > >> > >> ---------- Forwarded message ---------- > >> From: Vasile Gaburici <vgaburici(a)gmail.com> > >> Date: Tue, Aug 26, 2008 at 2:23 PM > >> Subject: Rebuilding pdftex gives ---! Must increase the hyph_size > >> (Fatal format file error; I'm stymied) > >> To: "pdftex(a)tug.org" <pdftex(a)tug.org> > >> > >> > >> I've applied a small patch (unrelated to hyphenation) to pdftex 1.40.9 > >> sources and I've successfully recompiled it. But when I try to use it > >> against the TeXLive 2008 tree (without overwriting the old binary), > >> I'm getting this: > >> > >> fmtutil: /home/vga/.texlive2008/texmf-var/web2c/pdftex/pdflatex.fmt installed. > >> ---! Must increase the hyph_size > >> (Fatal format file error; I'm stymied) > >> > >> Changing the hyph_size in texmf.cnf doesn's help. Any hints what could be wrong? > >> _______________________________________________ > >> ntg-pdftex mailing list > >> ntg-pdftex(a)ntg.nl > >> http://www.ntg.nl/mailman/listinfo/ntg-pdftex > > _______________________________________________ > > ntg-pdftex mailing list > > ntg-pdftex(a)ntg.nl > > http://www.ntg.nl/mailman/listinfo/ntg-pdftex > >

5 6

Re: [NTG-pdftex] Fwd: Rebuilding pdftex gives ---! Must increase the hyph_size (Fatal format file error; I'm stymied)
by Thanh Han The 26 Aug '08

26 Aug '08

yes, you need to change SELFAUTOPARENT to the actual path to texlive installation dir, too. What I gave in my previous was rather an example on how you can set TEXMFCNF to an explicit location. But this discussion belongs to texlive list, does it? Thanh On Tue, Aug 26, 2008 at 09:11:44PM +0300, Vasile Gaburici wrote: > There's no web2c under texmf-dist. The texmf.cnf from 2008/texmf/web2c > does get loaded, it just doesn't work properly, probably due the > $SELFAUTOPARENT business. The one that Fedora provides has hardcoded > paths. > > On Tue, Aug 26, 2008 at 9:06 PM, Philip TAYLOR (Ret'd) > <P.Taylor(a)rhul.ac.uk> wrote: > > > > > > Vasile Gaburici wrote: > > > >> export TEXMFCNF=/fc5/tl/2008/texmf/web2c > > > > Possibly TEXMFCNF=/fc5/tl/2008/texmf-dist/web2c ? > > > > Philip TAYLOR > > > >

1 0

Re: [NTG-pdftex] Fwd: Rebuilding pdftex gives ---! Must increase the hyph_size (Fatal format file error; I'm stymied)
by Thanh Han The 26 Aug '08

26 Aug '08

you can try to compile pdftex from sources, but without your patch. 1. if it works, then the problem is likely with the patch. 2. if not, the problem is likely with your tex config. Thanh On Tue, Aug 26, 2008 at 02:34:45PM +0300, Vasile Gaburici wrote: > I'm not sure that anyone reads pdftex(a)tug.org, so I'm trying my luck > on this list: > > ---------- Forwarded message ---------- > From: Vasile Gaburici <vgaburici(a)gmail.com> > Date: Tue, Aug 26, 2008 at 2:23 PM > Subject: Rebuilding pdftex gives ---! Must increase the hyph_size > (Fatal format file error; I'm stymied) > To: "pdftex(a)tug.org" <pdftex(a)tug.org> > > > I've applied a small patch (unrelated to hyphenation) to pdftex 1.40.9 > sources and I've successfully recompiled it. But when I try to use it > against the TeXLive 2008 tree (without overwriting the old binary), > I'm getting this: > > fmtutil: /home/vga/.texlive2008/texmf-var/web2c/pdftex/pdflatex.fmt installed. > ---! Must increase the hyph_size > (Fatal format file error; I'm stymied) > > Changing the hyph_size in texmf.cnf doesn's help. Any hints what could be wrong? > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

2 1

[pdftex-Bugs][2086] hyperref / marginpar
by pdftex-bugs＠sarovar.org 26 Aug '08

26 Aug '08

Bugs item #2086, was opened at 2008-08-25 16:44 >Status: Closed Priority: 3 Submitted By: Andreas Burkhardt (thongor) Assigned to: Nobody (None) Summary: hyperref / marginpar >Resolution: Wont Fix Group: None Category: None Initial Comment: \documentclass{article} \usepackage[ %colorlinks % funny, too ]{hyperref} \begin{document} I have here a small example with a funny effect. A Test \marginpar{link, broken into two lines} for line breaking an URL in two parts. \url{http://www.ctan.org/test/try/check/break/} And now look, what happens. Sorry about my bad english. \end{document} ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2008-08-26 11:46 Message: support for multi-line hyperlinks in pdftex is not robust enough for such cases. Unless macro packages have a workaround, this won't be fixed by pdftex. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2086&group_id=106

1 0

Fwd: Rebuilding pdftex gives ---! Must increase the hyph_size (Fatal format file error; I'm stymied)
by Vasile Gaburici 26 Aug '08

26 Aug '08

I'm not sure that anyone reads pdftex(a)tug.org, so I'm trying my luck on this list: ---------- Forwarded message ---------- From: Vasile Gaburici <vgaburici(a)gmail.com> Date: Tue, Aug 26, 2008 at 2:23 PM Subject: Rebuilding pdftex gives ---! Must increase the hyph_size (Fatal format file error; I'm stymied) To: "pdftex(a)tug.org" <pdftex(a)tug.org> I've applied a small patch (unrelated to hyphenation) to pdftex 1.40.9 sources and I've successfully recompiled it. But when I try to use it against the TeXLive 2008 tree (without overwriting the old binary), I'm getting this: fmtutil: /home/vga/.texlive2008/texmf-var/web2c/pdftex/pdflatex.fmt installed. ---! Must increase the hyph_size (Fatal format file error; I'm stymied) Changing the hyph_size in texmf.cnf doesn's help. Any hints what could be wrong?

1 0

[pdftex-Bugs][2086] hyperref / marginpar
by pdftex-bugs＠sarovar.org 25 Aug '08

25 Aug '08

Bugs item #2086, was opened at 2008-08-25 18:44 Status: Open Priority: 3 Submitted By: Andreas Burkhardt (thongor) Assigned to: Nobody (None) Summary: hyperref / marginpar Resolution: None Group: None Category: None Initial Comment: \documentclass{article} \usepackage[ %colorlinks % funny, too ]{hyperref} \begin{document} I have here a small example with a funny effect. A Test \marginpar{link, broken into two lines} for line breaking an URL in two parts. \url{http://www.ctan.org/test/try/check/break/} And now look, what happens. Sorry about my bad english. \end{document} ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2086&group_id=106

1 0

/Alt and /ActualText EMC should be versioned as PDF-1.5
by Vasile Gaburici 22 Aug '08

22 Aug '08

According to PDF 1.7 spec pages 942-944 a pdf that includes marked-content sequences containing /Alt and /ActualText should be versioned as PDF-1.5. Pdftex from Texlive 2008 (pdfTeX 3.1415926-1.40.9-2.2) only versions it as PDF-1.4. Thanks, Vasile

2 2

pdftex-1.40.9 release
by Thanh Han The 16 Aug '08

16 Aug '08

Hi, a new stable release is available at http://sarovar.org/frs/download.php/1240/pdftex-1.40.9.tar.bz2 -------------------------------------------------- pdfTeX 3.1415926-1.40.9 was released on 2008-08-16 -------------------------------------------------- - bugfixes: - pdf inclusion (inconsistent use of -DDISABLE_OUTLINE) - bug #2068 (cross-platform format dumping/undumping) - bug #2082 (font_dim[FONTNAME_CODE] not initialized) - bug #2083 (unchecked assignment) Thanh

1 0

Fwd: [png-mng-implement] libpng-1.0.38 and libpng-1.2.30 available
by Martin Schröder 15 Aug '08

15 Aug '08

---------- Forwarded message ---------- From: Glenn Randers-Pehrson <glennrp(a)gmail.com> Date: 2008/8/15 Subject: [png-mng-implement] libpng-1.0.38 and libpng-1.2.30 available To: PNG/MNG implementation discussion list <png-mng-implement(a)lists.sourceforge.net> libpng-1.0.38 and libpng-1.2.30 are available from ftp://ftp.simpleystems.org/pub/png/src/ and from http://libpng.sf.net There are many cosmetic changes from 1.2.29, and a potential DoS due to memory leaking on read error is fixed. Reding and writing of chunk length and chunk type are combined into a single i/o operation. Glenn ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ png-mng-implement mailing list png-mng-implement(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/png-mng-implement

1 0

[pdftex-Bugs][2083] problem with copyStream() (file pdftoepdf.cc)
by pdftex-bugs＠sarovar.org 12 Aug '08

12 Aug '08

Bugs item #2083, was opened at 2008-08-12 15:50 Status: Open Priority: 3 Submitted By: The Thanh Han (hanthethanh) Assigned to: The Thanh Han (hanthethanh) Summary: problem with copyStream() (file pdftoepdf.cc) Resolution: Accepted Group: None Category: PDF inclusion Initial Comment: the assignment pdflastbyte = pdfbuf[pdfptr - 1]; in copyStream() (file pdftoepdf.cc) may cause segfault, since there is no checking if pdfptr is > 0. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2083&group_id=106

1 0

[pdftex-Bugs][2082] font_dim[FONTNAME_CODE] not initialized (writefont.c)
by pdftex-bugs＠sarovar.org 12 Aug '08

12 Aug '08

Bugs item #2082, was opened at 2008-08-12 15:45 Status: Open Priority: 3 Submitted By: The Thanh Han (hanthethanh) Assigned to: The Thanh Han (hanthethanh) Summary: font_dim[FONTNAME_CODE] not initialized (writefont.c) Resolution: Accepted Group: None Category: Fonts Initial Comment: I found an issue with writefont.c: when a new en_entry is created, the value of font_dim[FONTNAME_CODE] is not initialized. For T1 fonts this is not a problem since all T1 fonts have fontname, but for TT fonts some weird fonts might not have [I ran into this problem during a test on some large TT fonts with valgrind] Here is the suggested patch: Index: source/src/texk/web2c/pdftexdir/writefont.c =================================================================== --- source/src/texk/web2c/pdftexdir/writefont.c (revision 508) +++ source/src/texk/web2c/pdftexdir/writefont.c (revision 509) @@ -81,7 +81,7 @@ fd->fn_objnum = 0; fd->all_glyphs = false; fd->write_ttf_glyph_names = false; - for (i = 0; i < INT_KEYS_NUM; i++) { + for (i = 0; i < FONT_KEYS_NUM; i++) { fd->font_dim[i].val = 0; fd->font_dim[i].set = false; } ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2082&group_id=106

1 0

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 10 Aug '08

10 Aug '08

On Sat, Aug 09, 2008 at 05:03:29PM +0100, Philip TAYLOR wrote: > >how about this: rename (or symlink) the ttc font to ttf, and > >document this trick in the manual. The way it works is more > >or less the same, but we don't have to change anything in > >the sources. > > I can see that renaming would work, but that > would prevent the .ttc font from working > in other applications that require and expect > a .ttc, but wouldn't symbolic linking cause > a problem in that it would then find /two/ > fonts, one .ttc and one .ttf, the former of > which it would treat as type-1 and the latter > as truetype ?! pdftex would look only for what is specified in map files. But I do also agree that this causes more confusion than simply applying the patch. Regards, Thanh

1 0

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 10 Aug '08

10 Aug '08

it looks like applying the patch and document it well would be simpler than any other hacks. Thanks for all comments. Regards, Thanh On Sun, Aug 10, 2008 at 09:22:34AM +0800, hzluo wrote: > Friends, > I forgot to mention some properties related to .ttc files. > For many .ttc files of CJK, all fonts in one .ttc file have > identical CJK glyphs. Only the latin glyphs are different. > But for latex systems, we use these fonts to typeset > CJK glyphs only. We have much better latin fonts > to typeset latin glyphs. As a result, supporting the > first font in .ttc file is good enough for most such > applications. > In addition, Windows does not support symbolic linking. > Only latest Windows versions support hardlink via junction, > but it can't work on early versions. > Certainly, supporting only the first font of .ttc file > is not equal to supporting .ttc file. Better way is to > add parameters to select fonts in .ttc file. But it needs > significant work. I do not know how to achieve this. > So, I think we can apply this patch, and claim in manual > that we support "the first font of .ttc file". Maybe someone > will work on a patch for full .ttc support later on, if s/he > is troubled by the problem. (If no one is troubled, > then no need to patch it, right? > - that's one of the spirit of opensource :) > > The aboves are only my two cents. > > Regards, > Hangzai > > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 10 Aug '08

10 Aug '08

On Sat, Aug 09, 2008 at 02:53:07PM +0200, Taco Hoekwater wrote: > Thanh Han The wrote: > > > >Your patch changes pdftex so that it will treat TTC like > >truetype font. While it works for your case, I am not > >confident that it's the right way to do that. Someone with a > >thorough understanding of TTC format can comment on this? > > IIRC, the patch will give access to the *first* font in the > collection, because that has an offset of zero (which makes > the first font in the ttc behave the same as a standalone ttf > font, when the ttc header is ignored). > > You could apply the patch but not document support for ttc > files (because the really patch doesn't implement that). This > gives a small subset of ttc functionality, but still better > than mishandling the format completely. how about this: rename (or symlink) the ttc font to ttf, and document this trick in the manual. The way it works is more or less the same, but we don't have to change anything in the sources. Thanh

3 2

Re: [NTG-pdftex] Question related to .ttc support
by Thanh Han The 09 Aug '08

09 Aug '08

On Fri, Aug 08, 2008 at 07:07:37PM +0800, hzluo wrote: > Friends, > I recently tested pdflatex with a Chinese font simsun.ttc, > pdflatex report the following error: > > !pdfTeX error: pdflatex (file simsun.ttc): cannot open Type 1 font file for > reading > > I checked the source code of pdflatex, found that pdflatex > only takes .ttf files as the truetype fonts, there is no test > for .ttc suffix. So, simsun.ttc is assumed to be a Type 1 font. > Apparently it is wrong. the manual says that if a fontfile has unknown extension, it will be treated as type1. Not quite right, but that's the expected bahaviour of pdftex in this case. > Is there any special reason to give up the .ttc support > in pdflatex? I found that dvipdfmx supports simsun.ttc smoothly, > so pdflatex should also do that, and it is quite simple. > I have attached a tiny patch to fix this. Could anyone confirm it? TTC is not truetype, but truetype collection. It's not supported by pdftex yet, since I don't know enough about this format yet and there seems to be very little interest in this format. Your patch changes pdftex so that it will treat TTC like truetype font. While it works for your case, I am not confident that it's the right way to do that. Someone with a thorough understanding of TTC format can comment on this? Regards, Thanh

2 1

Question related to .ttc support
by hzluo 08 Aug '08

08 Aug '08

Friends, I recently tested pdflatex with a Chinese font simsun.ttc, pdflatex report the following error: !pdfTeX error: pdflatex (file simsun.ttc): cannot open Type 1 font file for reading I checked the source code of pdflatex, found that pdflatex only takes .ttf files as the truetype fonts, there is no test for .ttc suffix. So, simsun.ttc is assumed to be a Type 1 font. Apparently it is wrong. Is there any special reason to give up the .ttc support in pdflatex? I found that dvipdfmx supports simsun.ttc smoothly, so pdflatex should also do that, and it is quite simple. I have attached a tiny patch to fix this. Could anyone confirm it? Regards, Hangzai

1 0

Including many files
by Martin Schröder 04 Aug '08

04 Aug '08

A follow-up to #2077: ------------------ File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> File: ./input/tuftecmr10-7683.pdf Graphic file (type pdf) <use ./input/tuftecmr10-7683.pdf, page 1> [7683] <./input/tuftecmr10-7684.pdf> <./input/tuftecmr10-7684.pdf> !pdfTeX error: pdflatex (file ./input/t): cannot find image file ==> Fatal error occurred, no output PDF file produced! ------------------ Looks like a silent buffer overflow somewhere. ./input/tuftecmr10-7684.pdf exists. Best Martin

1 0

[pdftex-Bugs][2077] pdf inclusion of the same file fails with the 12th copy
by pdftex-bugs＠sarovar.org 04 Aug '08

04 Aug '08

Bugs item #2077, was opened at 2008-08-04 14:34 >Status: Closed Priority: 3 Submitted By: Martin Schröder (oneiros) Assigned to: Nobody (None) Summary: pdf inclusion of the same file fails with the 12th copy >Resolution: Invalid Group: v1.40.3 Category: PDF inclusion Initial Comment: The included sources include the same file (hardlinked) 12 times. The 12th inclusion fails with <use ./input/tuftecmr10-11.pdf, page 1> [11 <./input/tuftecmr10-11.pdf>]Error: PDF file is damaged - attempting to reconstruct xref table... Error: Couldn't find trailer dictionary Error: Couldn't read xref table !pdfTeX error: pdflatex (file ./tuftecmr10-12.pdf): xpdf: reading PDF image fai led ==> Fatal error occurred, no output PDF file produced! Tested with 1.40.3, 1.40.9 and trunk. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-08-04 15:25 Message: Forget it, the setup is broken. %-) The main document is called tuftecmr10-12.tex and in the 12th run it tries to read tuftecmr10-12.pdf . This is in input/, but it is also just being created from tuftecmr10-12.tex . So pdftex finds ./tuftecmr10-12.pdf instead of input/tuftecmr10-12.pdf; and ./tuftecmr10-12.pdf is obviously broken as it hasn't been finished yet. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2077&group_id=106

1 0

Re: [NTG-pdftex] Future of http://scm.foundry.supelec.fr/svn/pdftex
by Thanh Han The 04 Aug '08

04 Aug '08

On Mon, Aug 04, 2008 at 02:37:09PM +0200, Martin Schroeder wrote: > 2008/8/4 Thanh Han The <hanthethanh(a)gmail.com>: > >> I'm asking because currently the pdftex sources at texlive are newer > >> than the ones at foundry. > > > > I will sync and release 1.40.9 after texlive 2008 is > > released. > > The binaries in texlive identify themselves as 1.40.9 I explained above > The development sources of pdftex are now where? texlive? foundry? Your machine? if you have anything to submit, submit them to supelec. Thanh

2 1

Re: [NTG-pdftex] Future of http://scm.foundry.supelec.fr/svn/pdftex
by Thanh Han The 04 Aug '08

04 Aug '08

On Mon, Aug 04, 2008 at 02:15:27PM +0200, Martin Schroeder wrote: > Thanh, > do you intend to use the svn repo at > http://scm.foundry.supelec.fr/svn/pdftex as the primary pdftex repo in > the future? yes > I'm asking because currently the pdftex sources at texlive are newer > than the ones at foundry. I will sync and release 1.40.9 after texlive 2008 is released. Thanh

2 1

[pdftex-Bugs][2077] pdf inclusion of the same file fails with the 12th copy
by pdftex-bugs＠sarovar.org 04 Aug '08

04 Aug '08

Bugs item #2077, was opened at 2008-08-04 14:34 Status: Open Priority: 3 Submitted By: Martin Schröder (oneiros) Assigned to: Nobody (None) Summary: pdf inclusion of the same file fails with the 12th copy Resolution: None Group: v1.40.3 Category: PDF inclusion Initial Comment: The included sources include the same file (hardlinked) 12 times. The 12th inclusion fails with <use ./input/tuftecmr10-11.pdf, page 1> [11 <./input/tuftecmr10-11.pdf>]Error: PDF file is damaged - attempting to reconstruct xref table... Error: Couldn't find trailer dictionary Error: Couldn't read xref table !pdfTeX error: pdflatex (file ./tuftecmr10-12.pdf): xpdf: reading PDF image fai led ==> Fatal error occurred, no output PDF file produced! Tested with 1.40.3, 1.40.9 and trunk. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2077&group_id=106

1 0

Future of http://scm.foundry.supelec.fr/svn/pdftex
by Martin Schröder 04 Aug '08

04 Aug '08

Thanh, do you intend to use the svn repo at http://scm.foundry.supelec.fr/svn/pdftex as the primary pdftex repo in the future? I'm asking because currently the pdftex sources at texlive are newer than the ones at foundry. Best Martin

1 0

[pdftex-Bugs][2068] format is not portable
by pdftex-bugs＠sarovar.org 13 Jul '08

13 Jul '08

Bugs item #2068, was opened at 2008-07-13 00:49 >Status: Closed Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) Summary: format is not portable >Resolution: Fixed Group: v1.40.8 Category: web2c Initial Comment: The format is not portable anymore. Tested with x86 and amd64 x86 with amd64 format: ------------------ This is pdfTeX, Version 3.1415926-1.40.8 (Web2C 7.5.7) /opt/tex/bin/i686-pc-linux-gnu/pdflatex: fatal: Could not undump 1 4-byte item(s). Breakpoint 2, 0xf7dbc2b6 in exit () from /lib/libc.so.6 (gdb) bt #0 0xf7dbc2b6 in exit () from /lib/libc.so.6 #1 0x080c1d61 in do_undump (p=0x83bce84 "", item_size=4, nitems=1, in_file=0x83cd7e0) at pdftexextra.c:1930 #2 0x080583a1 in loadfmtfile () at pdftexini.c:4294 #3 0x0805dc78 in mainbody () at pdftexini.c:5493 #4 0x080be9c6 in main (ac=Cannot access memory at address 0x2 ) at pdftexextra.c:422 (gdb) up ------------------ 4289 pdfmem = xreallocarray ( pdfmem , integer , pdfmemsize ) ; 4290 undumpint ( pdfmemptr ) ; 4291 {register integer for_end; k = 1 ;for_end = pdfmemptr - 1 ; if ( k <= 4292 for_end) do 4293 { 4294 undumpint ( pdfmem [k ]) ; 4295 } 4296 while ( k++ < for_end ) ;} 4297 undumpint ( objtabsize ) ; 4298 undumpint ( objptr ) ; (gdb) p k $5 = 17 ----------------- amd64 bin with x86 format: ------------------ This is pdfTeX, Version 3.1415926-1.40.8 (Web2C 7.5.7) !pdfTeX error: /opt/tex/bin/i686-pc-linux-gnu/pdflatex: unknown type of image ==> Fatal error occurred, no output PDF file produced! Breakpoint 2, 0x00002b17ff02d1e0 in exit () from /lib64/libc.so.6 (gdb) bt #0 0x00002b17ff02d1e0 in exit () from /lib64/libc.so.6 #1 0x000000000048a55d in pdftex_fail (fmt=0x57b41f "unknown type of image") at ../../../../src/texk/web2c/pdftexdir/utils.c:244 #2 0x00000000004a0bf3 in undumpimagemeta (pdfversion=4, pdfinclusionerrorlevel=0) at ../../../../src/texk/web2c/pdftexdir/writeimg.c:568 #3 0x000000000041194c in loadfmtfile () at pdftexini.c:4287 #4 0x00000000004161cf in mainbody () at pdftexini.c:5493 #5 0x0000000000481098 in main (ac=2, av=0x7fffabd1e858) at pdftexextra.c:422 ------------------ 4282 #ifdef INITEX 4283 trienotready = false 4284 #endif /* INITEX */ 4285 ; 4286 { 4287 undumpimagemeta ( eqtb [18248 ].cint , eqtb [18251 ].cint ) ; 4288 undumpint ( pdfmemsize ) ; 4289 pdfmem = xreallocarray ( pdfmem , integer , pdfmemsize ) ; 4290 undumpint ( pdfmemptr ) ; (gdb) p eqtb [18248 ] $1 = {gr = 8.491318209736172e-314, hh = {v = {LH = 6750208, RH = 4}, u = {B1 = 0, B0 = 103}}, u = { junk = 6750208, CINT = 4}, v = {junk = 6750208, QQQQ = {u = {B3 = 4 '\004', B2 = 0 '\0', B1 = 0 '\0', B0 = 0 '\0'}}}} (gdb) p eqtb [18251 ] $2 = {gr = 3.3350458750827492e-317, hh = {v = {LH = 6750208, RH = 0}, u = {B1 = 0, B0 = 103}}, u = { junk = 6750208, CINT = 0}, v = {junk = 6750208, QQQQ = {u = {B3 = 0 '\0', B2 = 0 '\0', B1 = 0 '\0', B0 = 0 '\0'}}}} ------------------ ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2008-07-13 13:28 Message: Fixed in 1.40.9 ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2008-07-13 10:02 Message: fixed by patch 2069 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-07-13 00:55 Message: I've attached x86 and amd64 binaries and formats for easier testing. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2068&group_id=106

1 0

[pdftex-Patches][2069] fix for bug 2068
by pdftex-patches＠sarovar.org 13 Jul '08

13 Jul '08

Patches item #2069, was opened at 2008-07-13 10:00 >Status: Closed Priority: 3 Submitted By: The Thanh Han (hanthethanh) >Assigned to: The Thanh Han (hanthethanh) Summary: fix for bug 2068 >Resolution: Accepted Group: v1.40.0 Category: None Initial Comment: a patch (for 1.40.8) to fix bug 2068 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=2069&group_id=106

1 0

[pdftex-Bugs][2068] format is not portable
by pdftex-bugs＠sarovar.org 13 Jul '08

13 Jul '08

Bugs item #2068, was opened at 2008-07-12 22:49 Status: Open Priority: 5 Submitted By: Martin Schröder (oneiros) >Assigned to: The Thanh Han (hanthethanh) Summary: format is not portable Resolution: Accepted Group: v1.40.8 Category: web2c Initial Comment: The format is not portable anymore. Tested with x86 and amd64 x86 with amd64 format: ------------------ This is pdfTeX, Version 3.1415926-1.40.8 (Web2C 7.5.7) /opt/tex/bin/i686-pc-linux-gnu/pdflatex: fatal: Could not undump 1 4-byte item(s). Breakpoint 2, 0xf7dbc2b6 in exit () from /lib/libc.so.6 (gdb) bt #0 0xf7dbc2b6 in exit () from /lib/libc.so.6 #1 0x080c1d61 in do_undump (p=0x83bce84 "", item_size=4, nitems=1, in_file=0x83cd7e0) at pdftexextra.c:1930 #2 0x080583a1 in loadfmtfile () at pdftexini.c:4294 #3 0x0805dc78 in mainbody () at pdftexini.c:5493 #4 0x080be9c6 in main (ac=Cannot access memory at address 0x2 ) at pdftexextra.c:422 (gdb) up ------------------ 4289 pdfmem = xreallocarray ( pdfmem , integer , pdfmemsize ) ; 4290 undumpint ( pdfmemptr ) ; 4291 {register integer for_end; k = 1 ;for_end = pdfmemptr - 1 ; if ( k <= 4292 for_end) do 4293 { 4294 undumpint ( pdfmem [k ]) ; 4295 } 4296 while ( k++ < for_end ) ;} 4297 undumpint ( objtabsize ) ; 4298 undumpint ( objptr ) ; (gdb) p k $5 = 17 ----------------- amd64 bin with x86 format: ------------------ This is pdfTeX, Version 3.1415926-1.40.8 (Web2C 7.5.7) !pdfTeX error: /opt/tex/bin/i686-pc-linux-gnu/pdflatex: unknown type of image ==> Fatal error occurred, no output PDF file produced! Breakpoint 2, 0x00002b17ff02d1e0 in exit () from /lib64/libc.so.6 (gdb) bt #0 0x00002b17ff02d1e0 in exit () from /lib64/libc.so.6 #1 0x000000000048a55d in pdftex_fail (fmt=0x57b41f "unknown type of image") at ../../../../src/texk/web2c/pdftexdir/utils.c:244 #2 0x00000000004a0bf3 in undumpimagemeta (pdfversion=4, pdfinclusionerrorlevel=0) at ../../../../src/texk/web2c/pdftexdir/writeimg.c:568 #3 0x000000000041194c in loadfmtfile () at pdftexini.c:4287 #4 0x00000000004161cf in mainbody () at pdftexini.c:5493 #5 0x0000000000481098 in main (ac=2, av=0x7fffabd1e858) at pdftexextra.c:422 ------------------ 4282 #ifdef INITEX 4283 trienotready = false 4284 #endif /* INITEX */ 4285 ; 4286 { 4287 undumpimagemeta ( eqtb [18248 ].cint , eqtb [18251 ].cint ) ; 4288 undumpint ( pdfmemsize ) ; 4289 pdfmem = xreallocarray ( pdfmem , integer , pdfmemsize ) ; 4290 undumpint ( pdfmemptr ) ; (gdb) p eqtb [18248 ] $1 = {gr = 8.491318209736172e-314, hh = {v = {LH = 6750208, RH = 4}, u = {B1 = 0, B0 = 103}}, u = { junk = 6750208, CINT = 4}, v = {junk = 6750208, QQQQ = {u = {B3 = 4 '\004', B2 = 0 '\0', B1 = 0 '\0', B0 = 0 '\0'}}}} (gdb) p eqtb [18251 ] $2 = {gr = 3.3350458750827492e-317, hh = {v = {LH = 6750208, RH = 0}, u = {B1 = 0, B0 = 103}}, u = { junk = 6750208, CINT = 0}, v = {junk = 6750208, QQQQ = {u = {B3 = 0 '\0', B2 = 0 '\0', B1 = 0 '\0', B0 = 0 '\0'}}}} ------------------ ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2008-07-13 08:02 Message: fixed by patch 2069 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2008-07-12 22:55 Message: I've attached x86 and amd64 binaries and formats for easier testing. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=2068&group_id=106

1 0