[jerryscript-debugger] Fail to add breakpoint on Chrome 66+

[haoxli]

Description

When using jerryscript-debugger-ts to debug ZJS on Linux and FRDM-K64F board, The breakpoint is added failed in Chrome Devtools (66+), which work well on Chrome 65.

Test Code

tests/test-buffer.js

Steps to Reproduction

Linux build for example:

1. git clone https://github.com/jimmy-huang/jerryscript
2. git checkout debugger-port
3. git clone https://github.com/jimmy-huang/zephyr.js
4. git checkout js-debugger
5. cd zephyr.js
6. source zjs-env.sh
7. make update
8. source deps/zephyr/zephyr-env.sh
9. Delete deps/jerryscript, and replace with the cloned one.
10. make BOARD=linux DEBUGGER=on
11. outdir/linux/release/jslinux tests/test-buffer.js --debugger

Start debugger proxy:
12. git clone https://github.com/jerryscript-project/jerryscript-debugger-ts
13. cd jerryscript-debugger-ts
14. yarn install
15. ./jerry-debugger.sh

Open Chrome 66:
16. Input chrome://inspect
17. Click Open dedicated DevTools for Node
18. Add breakpoint in source code

Actual Result

The breakpoint is added failed, it will display when the mouse clicks on code line, but disappear quickly.
And the terminal of jerry-debugger.sh output:

Expected Result

The breakpoint can be added in code.

Test Builds

Branch	Build ID	Target Device	Chrome	Date	Result
jimmy-huang/js-debugger	966904	Linux	66+	April 27, 2018	Fail
jimmy-huang/js-debugger	966904	Linux	65	April 27, 2018	Pass

[grgustaf]

Thanks for isolating to Chrome version, very interesting.