diff options
| author |  Googler <noreply@google.com> | 2018-05-23 12:32:07 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-05-23 12:33:20 -0700 |
| commit | 29eafdfe329b300dc42fddafde87bddae2f07a4c (patch) | |
| tree | 7b20b5796aeb5c32ce66c3160ebdb8f56d32106e /site/docs/android-instrumentation-test.md | |
| parent | 3e951fcb946b9f8efdef7a84a2fb0fe03ede010e (diff) | |
Initial implementation of a Skylark debug server API.
I've pulled out the API for separate review. It includes all
hooks from blaze/skylark used by the debugger.
Debuggable thread contexts are currently declared in 3 places:
- BuildFileAST (top-level evaluation of BUILD files)
- SkylarkRuleConfiguredTargetUtil (rules)
- SkylarkAspectFactory (aspects)
The purpose of declaring these contexts is so that the debugger
can track currently-active threads (and stop tracking them when
the task is completed).
Details of the actual debugging server are in unknown commit.
PiperOrigin-RevId: 197770547
Diffstat (limited to 'site/docs/android-instrumentation-test.md')
0 files changed, 0 insertions, 0 deletions