• Home
    • View
    • Login
    This page
    • Normal
    • Export PDF
    • Page Information

    Loading...
  1. Dashboard
  2. Undefined Space
  3. Loom
  4. Fiber Debugging Support

Page History

Versions Compared

Old Version 4

changes.mady.by.user Chris Plummer

Saved on Dec 13, 2018

compared with

New Version 5

changes.mady.by.user Chris Plummer

Saved on Dec 13, 2018

  • Previous Change: Difference between versions 3 and 4
  • Next Change: Difference between versions 5 and 6
  • View Page History

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • If the Debug Agent gets a BREAKPOINT event from JVMTI on a carrier thread, it will deliver that event to the debugger on the Fiber instead.
  • If you single step in a Fiber, this results in the Debug Agent enabling single stepping on the Carrier Thread that the Fiber is running on. When the JVMTI delivers the SINGLE_STEP event to the Debug Agent on the Carrier Thread, it is relayed to the debugger on the Fiber instead of the Carrier Thread.

In the future, we may decide to allow debuggers to be Fiber aware, possibly allowing for improved fiber debugging support. This would also require changes to JDI, JDWP, the Debug Agent, and JVMTI. We expect these design decisions to be driven by a combination of debugger user needs and what debugger vendors are willing to implement support for.


Overview
Content Tools
ThemeBuilder

Terms of Use
• License: GPLv2
• Privacy • Trademarks • Contact Us

Powered by a free Atlassian Confluence Open Source Project License granted to https://www.atlassian.com/software/views/opensource-community-additional-license-offer. Evaluate Confluence today.

  • Kolekti ThemeBuilder Powered by Atlassian Confluence 8.5.23
  • Kolekti ThemeBuilder printed.by.atlassian.confluence
  • Report a bug
  • Atlassian News
Atlassian
Kolekti ThemeBuilder EngineAtlassian Confluence
{"serverDuration": 207, "requestCorrelationId": "601807e91aee68f3"}