New issue
Advanced search Search tips

Issue 892653 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Debugger pauses at location w/o BP after "continue"

Reported by sandroto...@googlemail.com, Oct 5

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce the problem:
1. Open "bug.html"
2. Execute the following actions in the debugger, where the first column is the action, the second the line and the third the column:

set_bp 153 17
Reload page
set_bp 173 19
set_bp 74 5
step_out
step_in
step_over
step_over
step_over
step_over
continue

What is the expected behavior?
The debugger should not pause after the last "continue" action.

What went wrong?
The debugger paused at a location w/o a BP after a continue.

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

See devtools.mkv for video of actions. Excuse the non-minized JS, I wasn't sure which prerequisites have to be met to trigger this bug.
 
bug.html
122 bytes View Download
bug.js
5.1 KB View Download
devtools.mkv
5.3 MB Download
Owner: kozyatinskiy@chromium.org
Owner: kozy@chromium.org
Labels: Needs-Triage-M69
I was able to further minimize the actions. The required actions are:
set_bp 180:12
reload
set_bp 74:5
step_over
continue

The debugger then stops at 186:1, same as before.

I also noticed that the test execution is in fact incorrect (according to test262). I reported this at #8415 in the v8 bugtracker.
https://bugs.chromium.org/p/v8/issues/detail?id=8415
Managed to minify code. See new attached min.js and devtools.mkv for reproduction steps.
min.js
350 bytes View Download
min.html
122 bytes View Download
devtools_min.mkv
197 KB Download
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for the issue...

As per comment #5, tried to reproduce the issue on reported chrome 69.0.3497.100 using Ubuntu 17.10. Attaching screencast for reference.
Steps:
-----
1. Launched reported chrome
2. Downloaded given files and opened dev tools > sources 
3. clicked on 20 to set breakpoint 
As we have not seen foo value as per attached screencast on comment #5 

@Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end and verify this issue on latest chrome " https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists

Thanks..!

892653.webm
2.8 MB View Download
I have not tested this on latest dev version, however I verified that the bug still exists in version 70.0.3538.102.

Also, you need to load the script via the min.html file, accessing the .js file directly doesn't work.

Project Member

Comment 8 by sheriffbot@chromium.org, Nov 14

Labels: -Needs-Feedback
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
Labels: -Pri-2 Pri-1
Owner: alph@chromium.org
Status: Assigned (was: Unconfirmed)

Sign in to add a comment