Skip to content

wrong stepOver/stepInto behaviour in case of for loops #15

Open
Open
wrong stepOver/stepInto behaviour in case of for loops#15
Assignees
nulld
Labels
bugSomething isn't working

Description

@nulld
nulld
opened on Nov 9, 2018

debugger doesn't fall into for loop, using stepOver command, but surprisingly stepInto works.

				for (step in 0...steps.length)
				{
					if (steps[step] != updatedSteps[step])

Activity

  1. nulld
    self-assigned this
    on Nov 9, 2018
  2. Gama11
    added
    bugSomething isn't working
    on Feb 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions