[bug #39475] grep corrupts output _sometimes_ (not reproducible)

[NIck]

URL:
  <http://savannah.gnu.org/bugs/?39475>

                 Summary: grep corrupts output _sometimes_ (not reproducible)
                 Project: grep
            Submitted by: simnim
            Submitted on: Fri 12 Jul 2013 08:21:56 PM GMT
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Here's an abbreviated example command line that _sometimes_ gives me corrupt
output:
#When it feels like corrupting stuff ->
> cat $MY_FILE | grep '^something'
something       blah    blah    chr1    123456          1       0       0

#When it feels like doing it correctly
> cat $MY_FILE | grep '^something'
something       blah    blah    chr1    123456  -       1       0       0

The commands are identical. (Yes, I've strcomp'd them.)
Notice the missing dash after the 123456
Not good.

This is especially troublesome considering grep is essential.


> uname -a
Linux my_server 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

> grep --version
grep (GNU grep) 2.14
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others, see
<http://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS>.






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39475>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/