Repository navigation
Issues with .LOG Files #547
Description
[1] File: logs\dbg.log
Appends timings for every pass,
every time the same input file is run, without getting cleared out.
Bug: KEEPS GROWING IN SIZE.
[2] Duplicate Files: logs\dbg.log and output\dbg.log
The one in output\dbg.log DOES GET CLEANED OUT.
The other one does not.
Why are these files duplicated?
[3] Log directories: logs and output
.log files are produced in BOTH of these directories.
Why is that?
There are various ignored warnings and errors. For another day.
Summary: These logs provide useful information about the internals. NOT asking to get rid of them.
Amnon
Activity
ddehilster commentedon Oct 13, 2026
Checked on engine 4.2.11 by running the same input three times:
logs/dbg.loggrowing — fixed already: it is rewritten each run (1173 → 1169 → 1173 bytes).logs/dbg.logvsdbg.logelsewhere — not duplicates, despite the shared name.logs/dbg.logtimes the steps that parse the analyzer's own rule files at load (tokenize,retok,bigtok…);input/<file>_log/dbg.logtimes the analysis passes on that file.output/dbg.log(andoutput/def.log) are opened at startup, before the debug stream is redirected tologs/, and stay empty.logs/is the analyzer build (make_ana.log,cgerr.log, rule-file timings,file.log);input/<file>_log/is per-input results;output/only holds startup files (init.logfor the optionaluser.dll).I left the file names and locations alone: the VS Code extension reads several of them, and older tools may too, so moving them buys little and risks breaking something. Instead, VisualText/visualtext-files#233 documents every log file and what it holds on the Structure of Analyzer Projects help page.