Buggy logfile?

[mgree]

The logfile suggests that there is some kind of bug:

For some reason, the log-file parser noticed an extra 'close file' marker
It's possible that the filenames and line numbers reported near this are
This is likely a bug -- you should report it and include your log file!

I've attached the log file.

[dmwit]

Okay, there's a ton of stuff going on with this file. Thanks for sending it in.

The message you posted seems to be caused by the following snippet, starting on line 993:

[22pdfTeX warning (ext4): destination with the same identifier (name{lstnumber.
1}) has been already used, duplicate ignored

\AtBegShi@Output ...ipout \box \AtBeginShipoutBox 
                                                  \fi \fi 
l.1569 
       pdfTeX warning (ext4): destination with the same identifier (name{lstnum
ber.2}) has been already used, duplicate ignored

\AtBegShi@Output ...ipout \box \AtBeginShipoutBox 
                                                  \fi \fi 
l.1569 
       pdfTeX warning (ext4): destination with the same identifier (name{lstnum
ber.3}) has been already used, duplicate ignored

\AtBegShi@Output ...ipout \box \AtBeginShipoutBox 
                                                  \fi \fi 
l.1569 
       ] (/usr/local/texlive/2014/texmf-dist/tex/latex/listings/lstlang1.sty

Notice how the opening square bracket on the first line gets interrupted by the pdfTex warnings and doesn't get closed until 18 lines later! If I manually move that close bracket up to the first line, the tool doesn't complain -- though it still gets a lot of stuff wrong. I think the parser currently has some nonsense for handling square brackets with some stuff inside, but I don't think that stuff includes full on warnings and error messages -- just short interlopers like file names and types.

TeX's propensity for interrupting itself makes parsing really problematic. I'll play with a bit and see what can be done, though.

I also don't like what a terrible job it's doing of parsing the warnings. They're all getting marked as "unknown"s here -- the mark that my parser gives to things when it's thrown it's hands up in the air in frustration.

[mgree]

On May 19, 2016, at 5:23 PM, Daniel Wagner <notifications@github.commailto:notifications@github.com> wrote:

Okay, there's a ton of stuff going on with this file. Thanks for sending it in.

The message you posted seems to be caused by the following snippet, starting on line 993:

[22pdfTeX warning (ext4): destination with the same identifier (name{lstnumber.
1}) has been already used, duplicate ignored

\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.1569
pdfTeX warning (ext4): destination with the same identifier (name{lstnum
ber.2}) has been already used, duplicate ignored

\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.1569
pdfTeX warning (ext4): destination with the same identifier (name{lstnum
ber.3}) has been already used, duplicate ignored

\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.1569
] (/usr/local/texlive/2014/texmf-dist/tex/latex/listings/lstlang1.sty

Notice how the opening square bracket on the first line gets interrupted by the pdfTex warnings and doesn't get closed until 18 lines later! If I manually move that close bracket up to the first line, the tool doesn't complain -- though it still gets a lot of stuff wrong. I think the parser currently has some nonsense for handling square brackets with some stuff inside, but I don't think that stuff includes full on warnings and error messages -- just short interlopers like file names and types.

TeX's propensity for interrupting itself makes parsing really problematic. I'll play with a bit and see what can be done, though.

I know some of this is filed under ‘WONTFIX’, so no big deal. But since pulp itself told me to send it in, who am I to disagree? :)

I also don't like what a terrible job it's doing of parsing the warnings. They're all getting marked as "unknown"s here -- the mark that my parser gives to things when it's thrown it's hands up in the air in frustration.

If it would be useful, I can also pass along the files that caused this log. (And if you have a suggestion for a better package for code listings than ‘listings’, I’m all ears!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-220487287