Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix usage of StatementTag to fit with Truffle's expectations #67

Merged
merged 3 commits into from
Dec 1, 2016

Commits on Dec 1, 2016

  1. Mark only proper statements with StatementTag

    The semantics of StatementTag for the debugger requires that only classic statements are tagged. Otherwise, the stepping semantics are incorrect. Thus, expressions, nested in statements should not be tagged as statements.
    
    Signed-off-by: Stefan Marr <git@stefan-marr.de>
    smarr committed Dec 1, 2016
    Configuration menu
    Copy the full SHA
    4057ac2 View commit details
    Browse the repository at this point in the history
  2. Need to specify correct tag for special breakpoints

    Signed-off-by: Stefan Marr <git@stefan-marr.de>
    smarr committed Dec 1, 2016
    Configuration menu
    Copy the full SHA
    ac83517 View commit details
    Browse the repository at this point in the history
  3. Update expected data for dynamic metrics tests

    Necessary after changing the tagging of statements.
    
    Signed-off-by: Stefan Marr <git@stefan-marr.de>
    smarr committed Dec 1, 2016
    Configuration menu
    Copy the full SHA
    a6eb62e View commit details
    Browse the repository at this point in the history