AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

Fix indexing bug in regexp, part 2.

Browse Source 
The previous fix initialized the start index incorrectly.

BUG=

Review URL: https://chromiumcodereview.appspot.com/10834291

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@12302 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
This commit is contained in:
yangguo@chromium.org 2012-08-13 15:53:40 +00:00
parent e77f24f44e
commit 3605fcbe63
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/jsregexp.cc
View File

@ -748,12 +748,12 @@ RegExpImpl::GlobalCache::GlobalCache(Handle<JSRegExp> regexp,
// Set state so that fetching the results the first time triggers a call
// to the compiled regexp.
current_match_index_ = max_matches_;
current_match_index_ = max_matches_ - 1;
num_matches_ = max_matches_;
ASSERT(registers_per_match_ >= 2); // Each match has at least one capture.
ASSERT_GE(register_array_size_, registers_per_match_);
int32_t* last_match =
&register_array_[(current_match_index_ - 1) * registers_per_match_];
&register_array_[current_match_index_ * registers_per_match_];
last_match[0] = -1;
last_match[1] = 0;
}

2
test/mjsunit/regress/regress-crbug-142087.js
View File

@ -27,7 +27,7 @@
var string = "What are you looking for?";
var expected_match = [];
var expected_match = [""];
for (var i = 0; i < string.length; i++) {
expected_match.push("");
}