Posted on Aug 6, 2013 by
Quick Bear
When scanning files that do not end with EOL or whitespace, last line or last few characters of the file become corrupted, gibberish characters.
This happens on Windows with source files in ANSI (no UTF8) and line endings of CRLF. Adding blank newline to end of each file fixes this issue.
Comment #1
Posted on Aug 6, 2013 by Quick BearSorry this is a bug report for tabspace64.exe. Forgot to mention that.
Comment #2
Posted on Sep 7, 2013 by Happy Bird(No comment was entered for this change.)
Comment #3
Posted on Sep 7, 2013 by Helpful HippoSeems this is related to issue #216. At least I can not reproduce this anymore.
Status: Duplicate
Labels:
Type-Defect
Priority-Medium