Fix for issue 349: Make initial boundary check for BM text search.
authorlrn@chromium.org <lrn@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 19 May 2009 09:01:03 +0000 (09:01 +0000)
committerlrn@chromium.org <lrn@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 19 May 2009 09:01:03 +0000 (09:01 +0000)
commit2ff3901cf7ed6f0eaecd243b3e295f054690700b
treea5378598b7555bb0a40093a0e2e899cd0e8e3094
parentc27d0f7b4b83dc6f73e389664c1bef80408cb0fb
Fix for issue 349: Make initial boundary check for BM text search.
There was a case where the BMH algorithm bailed out exactly at the end of the string, and the BM algorithm that takes over wasn't expecting this.

Review URL: http://codereview.chromium.org/113575

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1995 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/runtime.cc
test/mjsunit/regress/regress-349.js [new file with mode: 0644]