Commit a50ee0e3 authored by Michael Achenbach's avatar Michael Achenbach Committed by Commit Bot

[foozzie] Don't provide stack locations for correctness fuzzing

Location information doesn't reveal interesting bugs, but leads to
tedious duplicates when the location information deviates.

Bug: chromium:1068003
Change-Id: I0b6d0ee28e1a3f370d19e5593484ee250fd6928f
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2148781
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#67139}
parent b78080dd
...@@ -87,7 +87,7 @@ Handle<JSMessageObject> MessageHandler::MakeMessageObject( ...@@ -87,7 +87,7 @@ Handle<JSMessageObject> MessageHandler::MakeMessageObject(
int bytecode_offset = -1; int bytecode_offset = -1;
Handle<Script> script_handle = isolate->factory()->empty_script(); Handle<Script> script_handle = isolate->factory()->empty_script();
Handle<SharedFunctionInfo> shared_info; Handle<SharedFunctionInfo> shared_info;
if (location != nullptr) { if (location != nullptr && !FLAG_correctness_fuzzer_suppressions) {
start = location->start_pos(); start = location->start_pos();
end = location->end_pos(); end = location->end_pos();
script_handle = location->script(); script_handle = location->script();
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment