Breakpoints are invisible after reopen ChromeDevTools

[qiaojingx]

Description

When using jerryscript-debugger.sh to debug with /bin/jerry executable + source.js inside JerryScript. Breakpoints will be invisible after reopening ChromeDevTools. If try to add the breakpoints again, it will prompt "breakpoint already enabled" in terminal, but still invisible in ChromeDevTools.

Test Code

JerryScript Debugger & Chrome DevTools Proxy;
jerryscript/test/debugger/do_finish.js

Steps to Reproduction

1. $ cd jerryscript
2. $ python tools/build.py --jerry-debugger=on --jerry-libc=off
3. $ ./build/bin/jerry --start-debug-server --log-level 2 test/debugger/do_finish.js
4. Have Chrome running and visit the URL chrome://inspect, and click "Open dedicated DevTools for Node."
5. $ cd jerryscript-debugger-ts
6. $ yarn install
7. $ ./jerry-debugger.sh
8. Add some breakpoints.
9. Reopen ChromeDevTools.

Actual Result

After Step9: No breakpoints display. If try to add breakpoints again, it will prompt "breakpoints already enabled" in terminal, but still invisible in ChromeDevTools.
Before reopen:

After reopen:

Error in terminal when add breakpoint:

Server < {"id":61,"method":"Debugger.setBreakpointByUrl","params":{"lineNumber":18,"url":"tests/debugger/do_finish.js","columnNumber":0,"condition":""}}
Server > {"id":61,"error":{"code":-32603,"message":"InternalError: Internal Error when calling 'Debugger.setBreakpointByUrl'","data":"breakpoint already enabled"}}

Expected Result

Breakpoints are visible after reopen ChromeDevTools. Breakpoints can removed and re-added.

Test Builds

Project	Commit Id	Target Device	Test Date	Result
jerryscript	d672d1e	Linux	May. 2, 2018	Fail
jerryscript-debugger-ts	ed66d7d	Linux	May. 2, 2018	Fail
Chrome	version 65	Linux	May. 2, 2018	Fail

Additional Information