DevTools: breakpoint isn't persisted across node.js sessions |
|||
Issue descriptionChrome Version: Google Chrome 59.0.3071.104 (Official Build) (64-bit) OS: Goobuntu node version: v8.1.4 What steps will reproduce the problem? This is the repro case: https://codereview.chromium.org/2976833002/ (1) Use chrome://inspect and start debugging with `node --inspect-brk migrate_test.js /path/to/test/name.html` (2) Add a breakpoint (3) End node process and start a new node process What is the expected result? There should be a breakpoint What happens instead? Most of the time there's no breakpoint. Once in a while, I'll see a bunch of breakpoints (I think the ones that I had set previously).
,
Aug 23 2017
,
Aug 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9f7971c9491e1856c83bcaa062f494bb948207f0 commit 9f7971c9491e1856c83bcaa062f494bb948207f0 Author: Eugene Ostroukhov <eostroukhov@chromium.org> Date: Thu Aug 24 18:34:15 2017 [DevTools] Retain file url to target path mapping Bug: 741198 Change-Id: I15945cfe4c7e54a263af3d9fba83130708b4cba7 Reviewed-on: https://chromium-review.googlesource.com/630579 Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org> Commit-Queue: Eugene Ostroukhov <eostroukhov@chromium.org> Cr-Commit-Position: refs/heads/master@{#497133} [modify] https://crrev.com/9f7971c9491e1856c83bcaa062f494bb948207f0/third_party/WebKit/Source/devtools/front_end/sdk/DebuggerModel.js
,
Aug 24 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by chenwilliam@chromium.org
, Aug 22 2017