[texhax] tex filename backtrace utility

[Uwe Lueck]

Hi Karl, hi Ron,

you might use Y&Y TeX for debugging, cf. this error message:

    ! Undefined control sequence.
    <argument> \headerps at out 
     {/burl at stx null def /BU.S { /burl at stx null def } de...

    C:/YANDY/TEXINPUT/breakurl.sty(303) : }

i.e., the error occurs at line 303 of breakurl.sty, error messages show filenames (with path) together with the line number ... so nice ...

Cheers, 

    Uwe.


-----Ursprüngliche Nachricht-----
Von: "Fehd, Ronald J. (CDC/CCHIS/NCPHI)" <rjf2 at CDC.GOV>
Gesendet: 16.02.2010 17:35:25
An: texhax at tug.org
Betreff: Re: [texhax] tex filename backtrace utility

>> Date: Sun, 14 Feb 2010 01:07:31 GMT
>> From: karl at freefriends.org (Karl Berry)
>> Subject: [texhax] tex filename backtrace utility
>> 
>> Sometimes it would be helpful for tex debugging to get a "backtrace"
>> of the files that tex is executing.  It could be something static, that
>> reads a .log file (or maybe .fls file from -recorder) and reports on
>> which files were opened and closed in some way that is readable for
>> deep nesting.
>> 
>> I seem to recall that auctex and presumably front ends have dealt with
>> extracting the filenames, at least, out of the mess of garbage printed
>> to the terminal on a typical run, parsing all the open/close parens,
>> but I've been unable to find anything that works as a separate utility.
>> 
>> Does anyone know of something to do this?
>> 
>> Failing anything else, I wonder about adding a new primitive to pdftex
>> to dump the input stack at any point.  Then we could get line numbers
>> too, I expect.
[Ron:]
>I am glad to see this suggestion as I have occasional problems
>identifying from which of my included files the error message is coming
>from.
[...]
>Ron Fehd  the {SAS} macro maven  CDC Atlanta GA USA RJF2 at cdc dot gov