Comment #2 on issue 4241 by [email protected]:
BreakLocation::BreakLocation may DCHECK/crash during
Debug::ClearAllBreakPoints
https://code.google.com/p/v8/issues/detail?id=4241#c2
The following revision refers to this bug:
https://chromium.googlesource.com/v8/v8.git/+/f283021f2dfb1daa0e271ac7d5b3676e39202553
commit f283021f2dfb1daa0e271ac7d5b3676e39202553
Author: yangguo <[email protected]>
Date: Thu Jun 25 10:43:32 2015
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.
[email protected]
BUG=v8:4241
LOG=N
Review URL: https://codereview.chromium.org/1210813002
Cr-Commit-Position: refs/heads/master@{#29286}
[modify]
http://crrev.com/f283021f2dfb1daa0e271ac7d5b3676e39202553/src/debug.cc
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
