I just tripped over something like this with grep v3.1-2 (Ubuntu 17.10 "artful"). the LC_ALL setting did not make a difference, and grep 3.1 passes the "test case" described in the bug description.
I have many text files, but one of them had a string of 49 \x00 chars. What confused me was the switch into binary mode happens on line 1,128,254, but the string of nulls is on line 1,128,436.
My method to find the triggering data was : `split -n 2 events.log` repeatedly: testing each half, discarding the half that passes and repeating until I had a failing text file I can manually examine.
I just tripped over something like this with grep v3.1-2 (Ubuntu 17.10 "artful"). the LC_ALL setting did not make a difference, and grep 3.1 passes the "test case" described in the bug description.
I have many text files, but one of them had a string of 49 \x00 chars. What confused me was the switch into binary mode happens on line 1,128,254, but the string of nulls is on line 1,128,436.
My method to find the triggering data was : `split -n 2 events.log` repeatedly: testing each half, discarding the half that passes and repeating until I had a failing text file I can manually examine.