Hi Brink,
I cannot replicate this behaviour on my system, I created a file exactly as you described and I get all the lines in a straight select from it.
My file looks like this - below if you copy and paste this in a HEX editor you will note the setup;
Text
Text1
A straight forward select returns as follows;
C:\projects\logparser>logparser "select * from crlf.txt"
WARNING: Input format not specified - using TEXTLINE input format.
LogFilename Index Text
------------------------------ ----- -----
C:\projects\logparser\crlf.txt 1 Text
C:\projects\logparser\crlf.txt 2 -
C:\projects\logparser\crlf.txt 3 -
C:\projects\logparser\crlf.txt 4 -
C:\projects\logparser\crlf.txt 5 Text1
Statistics:
-----------
Elements processed: 5
Elements output: 5
Execution time: 0.06 seconds
I did in another post note that I had similar different behaviour on a TSV file to someone else with the TAB characters - maybe something to do with my O/S or locale etc? I will look further into this.
You may want to try this as a workaround at the moment and see if it works for you.This does an inline manipulation of the unicode characters for you - although you will have to deal with
the fact that logparser represents null lines with a - character.
logparser "select replace_str(replace_str(text,'\u000d',''),'\u000a','\u000a\000d') as Tex from crlf.txt" -q:on -i:textline
This does an inline replace - although you will have to deal with the fact that logparser represents null lines with a - character.
If you can give an actual snippet from your log and what exactly you are trying to achieve, we will look into it.
Hope this helps.
Cheers, Dave