Debugging transpiled code changes the breakpoint line number

[xp500]

After applying #402 locally, I managed to get the stackdriver debugger to work. The problem is that if I set a breakpoint on a typescript file the breakpoint line will change when the breakpoint hits

Before hitting

After hitting

I believe that the problem is on https://github.com/GoogleCloudPlatform/cloud-debug-nodejs/blob/master/src/agent/v8/legacy-debugapi.ts#L461 and https://github.com/GoogleCloudPlatform/cloud-debug-nodejs/blob/master/src/agent/v8/inspector-debugapi.ts#L469 which changes the line number to the one set in the call frames. The problem is that the call frames refer to another file (the javascript file) and not the original typescript file where I set the breakpoint.

[DominicKramer]

Thank you for letting us know about this and for looking into this. As we work through this, we will keep this thread updated with status updates.

[dickfickling]

This has an additional impact which is that breakpoints set on a line after compiled file ends won't work at all. For example, my user.ts file has 519 lines. Compiled as user.js, it has 434 lines. I can't add a breakpoint to user.ts after line 434

[DominicKramer]

Thanks for letting us know about this. Based on this feedback, I have updated the priority of this issue.

[DominicKramer]

This issue has been fixed and released in version 2.6.0. If you are still encountering problems, please let me know. Thanks.

[dickfickling]

@DominicKramer The issue I reported above (unable to add breakpoints after end of original file) is still happening, although the original submitted issue (breakpoints moving) seems to be fixed.

[DominicKramer]

Thank you for letting us know about this issue. I have created issue #464 specifically to track not being able to add breakpoints after the end of the original file.