Incorrect & inconsistent debugger pause behaviour on return statements
Reported by
sandroto...@googlemail.com,
Oct 5
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 Steps to reproduce the problem: 1. Set BP at/before function call 2. Set BP after return statement in function 3. Load page, should stop at BP at function call 4. Hit continue What is the expected behavior? The debugger should stop at the BP inside the function, however it does not. Also, if the BP is created _after_ the debugger has already stopped at the function call, the behaviour is correct. What went wrong? The debugger behaviour is inconsistent depending on the time when the BP is created. In one case, the debugger skips the BP. Did this work before? N/A Chrome version: Version 69.0.3497.100 (Official Build) Channel: stable OS Version: Arch Linux x64 Flash Version: n/a
,
Oct 5
,
Oct 7
,
Nov 19
Thanks for the issue... Tried to reproduce the issue on reported chrome 69.0.3497.100 using Ubuntu 17.10. Attaching screenshot for reference. Steps: ----- 1. Launched reported chrome 2. Downloaded and kept in one folder the given file 3. Opened min.js file and Opened Dev tools > Sources 4. setted breakpoints as per given screencast As we have not seen function values at breakpoint 2 >return a; @Repoter: Could you please check the attached screenshot and let us know if anything missed from our end and verify this on latest chrome stabe, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Thanks..!
,
Nov 19
Please retry the steps using the provided min.html file, if you open min.js directly the debugger behavior changes.
,
Nov 19
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 5
,
Dec 5
,
Dec 6
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 10
This issue is marked as a release blocker with no milestone associated. Please add an appropriate milestone. All release blocking issues should have milestones associated to it, so that the issue can tracked and the fixes can be pushed promptly. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by binghamj@chromium.org
, Oct 5