# Just Launched: You can now import projects and releases from Google Code onto SourceForge

We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps.

## #577 Wrong "file" in error-log

pending
nobody
None
3
2012-10-17
2012-08-03
Pat Schweitzer
No

ok, this is a bit tricky to explain, but I will try.
I use a .tex file with several \include commands.
I quick compile and get a couple of errors, usually just bad boxes.
I like that clicking on them is possible. A line says something like:

conclusions.tex bad box line 922 Overfull \hbox (36.54646pt too wide) in paragraph

Then the next line says

main.tex bad box line 929 Overfull \hbox (39.23426pt too wide) in paragraph

Now, my main.tex doesn't even have that many lines. It's clear that it should say conclusion.tex.
Also clicking on it, jumps to main.tex, and not conclusion.tex

I did some investigations and it seem that whenever the previous bad box had a command
e.g. \emph{} or even a backet "(" in it, the Error message is broken. (That's just a guess, though)

Oh, and btw. what's up with all those assert failures? Are you aware of them? They are there
on and off and completely destroy TexStudio. It's mainly when I hover over bibtex links.
I'll open a proper bug as soon as I can actually describe it.

Ubuntu 10.04
SVN 3083

## Discussion

• Tim Hoffmann
2012-08-03

Parsing of TeX log files is a bit tricky. The file is not given directly at the error. Instead one hat to keep track of the files opened and closed during the log. Because of the output format it is sometimes difficult to do this in a reliable way.

Please post the relevant part of the log file, so we can check, where the parser fails.

@assert failures: Before discussing this here, you should open a separate bug report. Please provide also the following information. Did they just appear recently? If so, approximately since which revision? Please give the assertion message.
And have a look if it's related to one of these:
https://sourceforge.net/tracker/?func=detail&aid=3536611&group_id=250595&atid=1126426
https://sourceforge.net/tracker/?func=detail&aid=3543478&group_id=250595&atid=1126426

• Pat Schweitzer
2012-08-03

The assert failure thingy is probably this one:
https://sourceforge.net/tracker/?func=detail&aid=3536611&group_id=250595&atid=1126426

(That's why I asked for news...)

This is the latex output:
Underfull \hbox (badness 10000) in paragraph at lines 827--831
[]|\T1/cmr/m/n/12 The amount of real

Underfull \hbox (badness 6758) in paragraph at lines 827--831
\T1/cmr/m/n/12 the at-tack or de-fend

Underfull \hbox (badness 10000) in paragraph at lines 827--831
\T1/cmr/m/n/12 against it (de-pend-ing

Underfull \hbox (badness 3189) in paragraph at lines 827--831
\T1/cmr/m/n/12 whether it is the at-

Underfull \hbox (badness 10000) in paragraph at lines 827--831
\T1/cmr/m/n/12 tacker's of de-fender's

Underfull \hbox (badness 7925) in paragraph at lines 827--831
\T1/cmr/m/n/12 point of view) re-fer-

Underfull \hbox (badness 3019) in paragraph at lines 827--831
\T1/cmr/m/n/12 or soft-ware costs, ed-

Underfull \hbox (badness 10000) in paragraph at lines 827--831
\T1/cmr/m/n/12 u-ca-tional ex-penses,

And TexStudio has the following:
line 827: Underfull \hbox (badness 10000) in paragraph
line 827: Underfull \hbox (badness 6758) in paragraph
line 827: Underfull \hbox (badness 10000) in paragraph
line 827: Underfull \hbox (badness 3189) in paragraph
line 827: Underfull \hbox (badness 10000) in paragraph
line 827: Underfull \hbox (badness 7925) in paragraph
line 827: Underfull \hbox (badness 3019) in paragraph
line 827: Underfull \hbox (badness 10000) in paragraph

The first six link to the correct input file, then everything links to the main.

And as I said, this line has () in it...

I can also comment this line and look for a different occurence.

• Tim Hoffmann
2012-08-03

The closing bracket is indeed the problem

On file change "([filename]" is written to the output and a closing bracket at the and of the file:

(./foo.tex
[messages]
)

If the message now contains an unbalanced bracket, it's hard to tell, that it's from the message and not closing the file. Afaik you also cannot rely on formatting line breaks here. Latex logs are really not designed to be parsed automatically.

For the moment this won't be fixed. Maybe we can review the parser later. Even then it might be impossible to correctly parse all cases: How do we distinguish:
(./foo.tex [ some ) thing])
(./foo.tex [some]) [other ) thing]