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

@@ -70,9 +70,7 @@ BreakLocation::BreakLocation(Handle<DebugInfo> 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<DebugInfo> debug_info,