Avoid calling memchr with a zero range as this is undefined behavior.

Avoid calling memchr with a zero range as this is undefined behavior.

Calling memchr with a zero range is not explicitly specified to return NULL, and on Android arm64 it
returns an undefined value instead.  This CL ensures we don't call it with a zero range.

BUG=395678
LOG=N

[rmcilroy, 2014-07-30 14:25:46]

Yang, could you please take a look.  Thanks.

[Yang, 2014-07-30 14:28:53]

On 2014/07/30 14:25:46, rmcilroy wrote:
> Yang, could you please take a look.  Thanks.

LGTM!

[Yang, 2014-07-31 07:53:43]

The CQ bit was checked by yangguo@chromium.org

[Yang, 2014-07-31 07:53:46]

The CQ bit was unchecked by yangguo@chromium.org

[Yang, 2014-07-31 07:53:48]

The CQ bit was checked by yangguo@chromium.org

[Yang, 2014-07-31 07:53:55]

The CQ bit was unchecked by yangguo@chromium.org

[rmcilroy, 2014-07-31 11:24:53]

On 2014/07/31 07:53:55, Yang wrote:
> The CQ bit was unchecked by mailto:yangguo@chromium.org

The Android team fixed the issue, however should I still land this to be safe? 
Can I land it now while the tree is still throttled, it should be safe?

[rmcilroy, 2014-07-31 16:30:48]

On 2014/07/31 11:24:53, rmcilroy wrote:
> On 2014/07/31 07:53:55, Yang wrote:
> > The CQ bit was unchecked by mailto:yangguo@chromium.org
> 
> The Android team fixed the issue, however should I still land this to be safe?

> Can I land it now while the tree is still throttled, it should be safe?

Dropping this since it has been fixed by Android.