diff options
| author | hashimoto@chromium.org <hashimoto@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-11 10:43:54 +0000 |
|---|---|---|
| committer | hashimoto@chromium.org <hashimoto@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-11 10:43:54 +0000 |
| commit | 1b0c379fa8b3da635fa35e3af1c078178460e935 (patch) | |
| tree | 1dc54302100ed5bf044030fb083eb71ae4a4ee5d /third_party/lzma_sdk/Alloc.h | |
| parent | 6966445f8095242e593b26b568f54eb604f6f62a (diff) | |
| download | chromium_src-1b0c379fa8b3da635fa35e3af1c078178460e935.zip chromium_src-1b0c379fa8b3da635fa35e3af1c078178460e935.tar.gz chromium_src-1b0c379fa8b3da635fa35e3af1c078178460e935.tar.bz2 | |
Revert 211050 "Handle null char in the middle of text in custom ..."
r211050 seems to be the cause of Linux ASAN bot failure.
> Handle null char in the middle of text in custom spellcheck dictionary engine
>
> The code in custom spellcheck dictionary erroneously assumes that null char
> terminates the string. Other code does not make this assumption, however, and
> passes misspelling offsets to custom spellcheck dictionary that are past the
> position of the null char. This causes an exception. The fix is to not use the
> null char as string terminator in custom spellcheck dictionary engine. This is
> accomplished by switching from a string16(char16* buffer) to a string16(char*
> buffer, int length) constructor.
>
> TEST=CustomDictionaryTest.HandleNullCharacters
> BUG=258550
>
> Review URL: https://chromiumcodereview.appspot.com/18497015
BUG=259290
TBR=rouslan@chromium.org
Review URL: https://codereview.chromium.org/18036005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@211056 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/lzma_sdk/Alloc.h')
0 files changed, 0 insertions, 0 deletions