|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#36820: closed (grep "[[:cntrl:]]" /proc/1/cmdline works on 2.20 but not 3.3) |
Date: | Sat, 27 Jul 2019 17:17:03 +0000 |
Your message dated Sat, 27 Jul 2019 10:16:00 -0700 with message-id <address@hidden> and subject line Re: bug#36820: grep "[[:cntrl:]]" /proc/1/cmdline works on 2.20 but not 3.3 has caused the debbugs.gnu.org bug report #36820, regarding grep "[[:cntrl:]]" /proc/1/cmdline works on 2.20 but not 3.3 to be marked as done. (If you believe you have received this mail in error, please contact address@hidden.) -- 36820: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36820 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: grep "[[:cntrl:]]" /proc/1/cmdline works on 2.20 but not 3.3 Date: Sat, 27 Jul 2019 07:52:37 +0800 # using grep 2.20 ...# grep "[[:cntrl:]]" /proc/1/cmdlineBinary file /proc/1/cmdline matchesJeff# using grep 3.3 or above 2.20 ...# grep "[[:cntrl:]]" /proc/1/cmdline... nothing returnedMy best.,
--- End Message ---
--- Begin Message ---Subject: Re: bug#36820: grep "[[:cntrl:]]" /proc/1/cmdline works on 2.20 but not 3.3 Date: Sat, 27 Jul 2019 10:16:00 -0700 This is documented behavior; the grep manual says that when grep is reading a binary file it "may treat non-text bytes as line terminators". User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 You can use grep's -a (--text) option to if you want to match null bytes.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |