From f283021f2dfb1daa0e271ac7d5b3676e39202553 Mon Sep 17 00:00:00 2001 From: yangguo Date: Thu, 25 Jun 2015 03:43:32 -0700 Subject: [PATCH] Debugger: remove bogus assertion in BreakLocation constructor. Currently DebugInfo objects can be created independently from whether the debugger is active. When tearing down the isolate, we would go through DebugInfo objects and iterate through break locations, causing this assertion to fail. R=ulan@chromium.org BUG=v8:4241 LOG=N Review URL: https://codereview.chromium.org/1210813002 Cr-Commit-Position: refs/heads/master@{#29286} --- src/debug.cc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/debug.cc b/src/debug.cc index d966b6e..c414e23 100644 --- a/src/debug.cc +++ b/src/debug.cc @@ -70,9 +70,7 @@ BreakLocation::BreakLocation(Handle debug_info, RelocInfo* rinfo, data_(rinfo->data()), original_data_(original_rinfo->data()), position_(position), - statement_position_(statement_position) { - DCHECK(debug_info_->GetIsolate()->debug()->is_active()); -} + statement_position_(statement_position) {} BreakLocation::Iterator::Iterator(Handle debug_info, -- 2.7.4