In NonAllocatingMap, remove asserts around key/value length.

In NonAllocatingMap, remove asserts around key/value length.

Since the data is stored using strncpy they are merely advisory in debug mode.

BUG=https://code.google.com/p/chromium/issues/detail?id=298225
R=mark@chromium.org

Committed: https://code.google.com/p/google-breakpad/source/detail?r=1219

[rsesek]

Thoughts on this? I could have clients pre-truncate the data, but since all
existing clients will want assert-free-truncation, it makes more sense to do it
here I think. Clients can always assert against
NonAllocatingMap<X,Y,Z>::value_size if they want to explicitly protect against
truncation.

[Mark Mentovai]

I guess if key_size and value_size are invisible to the clients that are setting
the keys and values since they’re an implementation choice that can be made and
changed elsewhere, it’s kind of unfair to assert when there’s a length
violation. LGTM.

[rsesek]

Committed patchset #1 manually as r1219 (presubmit successful).