[Design doc] Debugging Protocol for Skylark and Bazel Integration

[tony.a...@gmail.com]

Hi all,

Recently I've been hacking around with adding a protobuf-based debugging protocol to the Skylark interpreter in Bazel, along with a companion debugger extension in VS Code, to give Skylark rule authors debugging capabilities that they would expect while developing their rules—setting breakpoints during a build, stepping through code, viewing the state of variables in your evaluation environment and so forth.

A formal design doc can be found here: http://goo.gl/oauzKq

Though it mentions VS Code a bit, that's just because it's the development environment that I happen to use regularly (and because the debugging extensions are fairly straightforward to implement). Support for other IDEs would naturally follow.

Thanks!

—Tony

[Ulf Adams]

That's awesome! Thanks! I added a couple of comments to the doc.

--
You received this message because you are subscribed to the Google Groups "bazel-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-dev+unsubscribe@googlegroups.com.
To post to this group, send email to baze...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-dev/afb5312a-ab99-4e75-a319-896a2a2889d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[itt...@wix.com]

Hi,

This will take a long time to materialize?

Can't help right now but really really waiting for it

On Friday, November 3, 2017 at 10:28:39 PM UTC+2, Ulf Adams wrote:

That's awesome! Thanks! I added a couple of comments to the doc.

On Fri, Nov 3, 2017 at 7:07 AM, <tony.a...@gmail.com> wrote:

Hi all,

Recently I've been hacking around with adding a protobuf-based debugging protocol to the Skylark interpreter in Bazel, along with a companion debugger extension in VS Code, to give Skylark rule authors debugging capabilities that they would expect while developing their rules—setting breakpoints during a build, stepping through code, viewing the state of variables in your evaluation environment and so forth.

A formal design doc can be found here: http://goo.gl/oauzKq

Though it mentions VS Code a bit, that's just because it's the development environment that I happen to use regularly (and because the debugging extensions are fairly straightforward to implement). Support for other IDEs would naturally follow.

Thanks!

—Tony

--
You received this message because you are subscribed to the Google Groups "bazel-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to bazel-dev+...@googlegroups.com.