1. 10 Feb, 2017 1 commit
  2. 09 Feb, 2017 2 commits
  3. 08 Feb, 2017 1 commit
    • kozyatinskiy's avatar
      [inspector] support for nested scheduled breaks · 56bf7dbd
      kozyatinskiy authored
      In current implementation we don't support nested scheduled break at all. If one break was scheduled inside another and second one doesn't produce actual break (execution was in blackboxed code or no JavaScript was executed) then second one will clear first scheduled break even if any not blackboxed JavaScript will be executed later.
      
      Ambiguous break reason is added for the case when we have more then one scheduled reason. "auxData" in this case contains object with array of { reason: reason, auxData: auxData } objects for each reason in 'reasons' property.
      
      BUG=chromium:632405
      
      Review-Url: https://codereview.chromium.org/2678313002
      Cr-Commit-Position: refs/heads/master@{#43021}
      56bf7dbd
  4. 03 Feb, 2017 3 commits
  5. 27 Jan, 2017 1 commit
    • clemensh's avatar
      [inspector] Expose GetPossibleBreakpoints for wasm · c6663ef1
      clemensh authored
      and add an inspector test for it. Also test that a breakpoint can be
      set on each reported position, and that it is also hit during
      execution.
      This CL also fixes two little things which were uncovered by the new
      test.
      
      R=yangguo@chromium.org, titzer@chromium.org, kozyatinskiy@chromium.org
      BUG=v8:5822
      
      Review-Url: https://codereview.chromium.org/2655653003
      Cr-Commit-Position: refs/heads/master@{#42722}
      c6663ef1
  6. 24 Jan, 2017 1 commit
    • kozyatinskiy's avatar
      [inspector] implemented blackboxing inside v8 · ac50c79a
      kozyatinskiy authored
      V8 has internal mechanism to ignore steps and breaks inside internal scripts, in this CL it's reused for blackboxing implementation.
      Advantages:
      - much faster blackboxing implementation (before we at least wrap and collect current call stack for each step),
      - get rid of StepFrame action and potential pause in blackboxed code after N StepFrame steps,
      - simplification of debugger agent logic.
      Disadvtanges:
      - currently when user was paused in blackboxed code (e.g. on breakpoint) and then makes step action, debugger ignores blackboxed state of the script and allows to use step actions as usual - this behavior is regressed, we still able to support it on frontend side.
      
      Current state and proposed changes for blackboxing: https://docs.google.com/document/d/1hnzaXPAN8_QC5ENxIgxgMNDbXLraM_OXT73rAyijTF8/edit?usp=sharing
      
      BUG=v8:5842
      R=yangguo@chromium.org,dgozman@chromium.org,alph@chromium.org
      
      Review-Url: https://codereview.chromium.org/2633803002
      Cr-Commit-Position: refs/heads/master@{#42614}
      ac50c79a
  7. 18 Jan, 2017 1 commit
  8. 19 Dec, 2016 3 commits
  9. 12 Dec, 2016 1 commit
  10. 06 Dec, 2016 1 commit
    • clemensh's avatar
      [inspector] Introduce debug::WasmScript · 12cdb31b
      clemensh authored
      *and* report all "virtual" wasm scripts right when the wasm script is
      registered at the inspector.
      
      WasmScript is a subtype of Script, with the cast checking that it is
      actually a wasm script.
      This layout makes it quite easy to implement functionality that is only
      available for wasm scripts, and allows to later directly use the
      WasmCompiledModule instead of the i::Script for backing the
      debug::WasmScript. We might also add virtual methods to
      provide different implementations for GetSourcePosition, Source and
      others.
      
      DisassembleWasmFunction now also becomes a method of this class instead
      of a static function on the DebugInterface.
      
      The WasmTranslation now uses the new WasmScript type instead of the
      Script wrapper, and also registers all virtual wasm scripts immediately
      when the wasm script is made public to the inspector (when the wasm
      module is created).
      
      R=yangguo@chromium.org,dgozman@chromium.org,titzer@chromium.org
      BUG=chromium:613110,chromium:659715
      
      Review-Url: https://codereview.chromium.org/2531163010
      Cr-Commit-Position: refs/heads/master@{#41519}
      12cdb31b
  11. 05 Dec, 2016 2 commits
    • clemensh's avatar
      [debug] Remove DebugInterface class · e6bd3063
      clemensh authored
      It only contained type definitions and static functions, so we
      can also just make it a namespace.
      
      R=kozyatinskiy@chromium.org, yangguo@chromium.org
      
      Review-Url: https://codereview.chromium.org/2549133002
      Cr-Commit-Position: refs/heads/master@{#41501}
      e6bd3063
    • clemensh's avatar
      [inspector] Split off interface-types.h · f5fb2da6
      clemensh authored
      This CL adds a new header src/debug/interface-types.h, moves the
      definition of Location from the debug-interface.h to this new header,
      and adds a new definition for the WasmDisassembly types.
      This allows to use the types in other implementation files or headers
      without having to include the entire debug-interface.h, reducing build
      dependencies and compile time (especially for incremental builds).
      
      The WasmDisassembly type replaces the old
      std::pair<std::string, std::vector<std::tuple<...>>>, which was a bit
      hard to unravel.
      
      R=yangguo@chromium.org, kozyatinskiy@chromium.org, titzer@chromium.org
      
      Review-Url: https://codereview.chromium.org/2529383002
      Cr-Commit-Position: refs/heads/master@{#41488}
      f5fb2da6
  12. 23 Nov, 2016 1 commit
  13. 22 Nov, 2016 1 commit
  14. 16 Nov, 2016 3 commits
    • clemensh's avatar
      [inspector] Introduce translation of wasm frames · d4a42a5f
      clemensh authored
      This allows to show wasm source (disassembled wasm code) in DevTools.
      See design doc for details.
      
      More tests for the disassembly will have to follow. Also, the text
      format (generated by V8) will be changed.
      
      BUG=chromium:659715
      R=yangguo@chromium.org, kozyatinskiy@chromium.org, titzer@chromium.org, dgozman@chromium.org
      
      Review-Url: https://codereview.chromium.org/2493773003
      Cr-Commit-Position: refs/heads/master@{#41055}
      d4a42a5f
    • clemensh's avatar
      [inspector] Change ScriptBreakpoint to include scriptId · 764371bc
      clemensh authored
      The ScriptBreakpoint struct was before just holding line, column and
      condition. It now additionally holds the scriptId.
      This encapsulates information nicer, and allows for easier translation
      of wasm locations, since one struct now holds all information needed
      for the translation.
      
      BUG=chromium:659715
      R=yangguo@chromium.org, kozyatinskiy@chromium.org
      
      Review-Url: https://codereview.chromium.org/2491133003
      Cr-Commit-Position: refs/heads/master@{#41044}
      764371bc
    • jgruber's avatar
      [debug-wrapper] Further extend the debug wrapper · b06c4ce5
      jgruber authored
      This CL further extends the debug wrapper, migrates around 60 tests, and
      removes a few tests that use functionality we will not support anymore.
      
      In more detail:
      
      * Removed tests that use:
        * enable/disable individual breakpoints
        * invocationText()
        * the ScriptCollected event
        * showBreakPoints
        * evalFromScript (and similar)
        * mirror.constructedBy and mirror.referencedBy
        * event_data.promise()
      * Some frame.evaluate uses were adapted since due to differences between
        remote objects (inspector) and mirrors. For instance, exceptions are
        currently not recreated exactly, since the inspector protocol does not
        give us the stack and message separately. Other objects (such as
        'this' in debug-evaluate-receiver-before-super) need to be explicitly
        converted to a string before the test works correctly.
      * Ensure that inspector stores the script before sending ScriptParsed and
        ScriptFailedToParse events in order to be able to use the script from
        within those events.
      * Better remote object reconstruction (e.g. for undefined and arrays).
      * New functionality in wrapper:
        * debuggerFlags().breakPointsActive.setValue()
        * scripts()
        * execState.setVariableValue()
        * execState.scopeObject().value()
        * execState.scopeObject().property()
        * execState.frame().allScopes()
        * eventData.exception()
        * eventData.script()
        * setBreakPointsActive()
      
      BUG=v8:5530
      
      Review-Url: https://codereview.chromium.org/2497973002
      Cr-Commit-Position: refs/heads/master@{#41019}
      b06c4ce5
  15. 15 Nov, 2016 1 commit
    • clemensh's avatar
      [inspector] Fix and refactor String16 · c9c6c1a3
      clemensh authored
      This CL defines move semantics for String16, and fixes issues with the
      hash code not being set correctly on swap or copy.
      It also extends the interface by a few handy templates.
      All this functionality will be used for the wasm translations, where
      String16s are often concatenated and used as keys in hash tables.
      
      BUG=chromium:659715
      R=yangguo@chromium.org, kozyatinskiy@chromium.org
      
      Review-Url: https://codereview.chromium.org/2493723003
      Cr-Commit-Position: refs/heads/master@{#41007}
      c9c6c1a3
  16. 10 Nov, 2016 1 commit
    • jgruber's avatar
      [inspector] Add exception caught/uncaught status to protocol · fab116be
      jgruber authored
      This adds information about an exception's caught/uncaught status to the
      Runtime.paused event in the data parameter:
      
      {
          "method": "Debugger.paused",
          "params": {
              "callFrames": [
      	    [...]
              ],
              "data": {
                  "description": "666",
                  "type": "number",
                  "uncaught": true,  <---
                  "value": 666
              },
              "hitBreakpoints": [],
              "reason": "exception"
          }
      }
      
      BUG=v8:5530
      
      Review-Url: https://codereview.chromium.org/2488733003
      Cr-Commit-Position: refs/heads/master@{#40875}
      fab116be
  17. 04 Nov, 2016 2 commits
  18. 03 Nov, 2016 1 commit
  19. 19 Oct, 2016 2 commits
  20. 18 Oct, 2016 1 commit
  21. 26 Sep, 2016 1 commit
  22. 22 Sep, 2016 1 commit
  23. 21 Sep, 2016 4 commits
  24. 15 Sep, 2016 1 commit
  25. 14 Sep, 2016 1 commit
  26. 06 Sep, 2016 1 commit
  27. 01 Sep, 2016 1 commit