[Bug 1621226] Re: grep does not output null when -o -z is used

[Jarno Suni]

** Description changed:

  Impact
  
  Grepping null terminated records with -o option does not work. There may
  be a newline in a matched string, so the output may be ambiguous as the
- matched parts are separated by newline.
+ matched parts are separated by newline. This bug prevents users from
+ using grep in some scripts that they want to work in all supported
+ releases.
  
  Test Case
  
  $ printf 'a\0b\0b1' | grep --null-data b | hexdump -C
  00000000  62 00 62 31 00                                    |b.b1.|
  00000005
  
  but
  
  $ printf 'a\0b\0b1' | grep -o --null-data b | hexdump -C
  00000000  62 0a 62 0a                                       |b.b.|
  00000004
  
  Expected result:
  00000000  62 00 62 00                                       |b.b.|
  00000004
  
  Regression Potential
  
  Not remarkable. Scripts using -o -z are broken anyway with the broken
  grep.
  
  This is fixed in Xenial, but IMO should be fixed in Trusty, too.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grep 2.16-1
  ProcVersionSignature: Ubuntu 4.4.0-37.56~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep  7 22:48:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (717 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1)
  SourcePackage: grep
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1621226

Title:
  grep does not output null when -o -z is used

Status in grep package in Ubuntu:
  Fix Released
Status in grep source package in Trusty:
  New

Bug description:
  Impact

  Grepping null terminated records with -o option does not work. There
  may be a newline in a matched string, so the output may be ambiguous
  as the matched parts are separated by newline. This bug prevents users
  from using grep in some scripts that they want to work in all
  supported releases.

  Test Case

  $ printf 'a\0b\0b1' | grep --null-data b | hexdump -C
  00000000  62 00 62 31 00                                    |b.b1.|
  00000005

  but

  $ printf 'a\0b\0b1' | grep -o --null-data b | hexdump -C
  00000000  62 0a 62 0a                                       |b.b.|
  00000004

  Expected result:
  00000000  62 00 62 00                                       |b.b.|
  00000004

  Regression Potential

  Not remarkable. Scripts using -o -z are broken anyway with the broken
  grep.

  This is fixed in Xenial, but IMO should be fixed in Trusty, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: grep 2.16-1
  ProcVersionSignature: Ubuntu 4.4.0-37.56~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep  7 22:48:42 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (717 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1)
  SourcePackage: grep
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1621226/+subscriptions