Once NUL character is encountered by this tool, it stops parsing the file and rest of the log file is ignored

[inspire99]

Once NUL character is encountered by this tool, it stops parsing the file and rest of the log file is ignored.

Sometimes, server logs might contain junk characters.. such as NUL character.
This tool has a bug where in it stops parsing the rest of the file and so sometimes, analysis is not complete.
There are workarounds, where file cleanup is required, for example, thanks to: http://security102.blogspot.com/2010/04/findreplace-of-nul-objects-in-notepad.html

With this, NUL objects are removed.. and then again the log file is imported into LogAnalyzer.. and LogAnalyzer can work fine.

[pbek]

Thank you for your suggestion. Pull requests are welcome. 😁