News for hackers. Stuff that matters.
Re:Tracking down a segfault in grep by 0x0 on Wednesday February 18, 2015 @08:12AM (#9068290)
Yep, and the crash reporter gives:

  Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
  0   libsystem_platform.dylib      	0x00007fffxxxxxxxx _platform_memchr$VARIANT$Haswell + 101
  1   libsystem_c.dylib             	0x00007fffxxxxxxxx __sfvwrite + 268
  2   libsystem_c.dylib             	0x00007fffxxxxxxxx fwrite + 142
  3   grep                          	0x00000001xxxxxxxx 0x10xxxxxxx + 13606
  4   grep                          	0x00000001xxxxxxxx 0x10xxxxxxx + 12465
  5   grep                          	0x00000001xxxxxxxx 0x10xxxxxxx + 8190
  6   libdyld.dylib                 	0x00007fffxxxxxxxx start + 1
A different version from yours though:

  what /usr/bin/grep
    PROGRAM:grep  PROJECT:bsdgrep-17
Re:Tracking down a segfault in grep by masklinn on Wednesday February 18, 2015 @08:17AM (#9068304)
Is it possible that you're using Yosemite and TFA uses Mavericks? I have the same bsdgrep-16 on Mavericks.
Re:Tracking down a segfault in grep by loadzero on Wednesday February 18, 2015 @08:46AM (#9068427)
Yep - I'm on 10.9.5
Re:Tracking down a segfault in grep by 0x0 on Wednesday February 18, 2015 @09:02AM (#9068497)
yep, 10.10.2 here