Expand and organize repo #47
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - [Chrome Debugging Protocol](https://chromedevtools.github.io/debugger-protocol-viewer/) | ||
| - [V8 Debugging Protocol](https://github.com/v8/v8/wiki/Debugging-Protocol) | ||
|
|
||
| Node currently relies on V8's internal Debug API and associated commands and events. The Debug API is published at [v8/include/v8-debug.h](https://gihtub.com/v8/v8/blob/master/include/v8-debug.h), and the message protocol is documented in prose in [the V8 wiki](https://github.com/v8/v8/wiki/Debugging-Protocol) and in code in [v8/src/debug/debug.js#L2341-2372](https://github.com/v8/v8/blob/master/src/debug/debug.js#L2341-L2372). |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
joshgav
force-pushed
the
foundation
branch
2 times, most recently
from
301a507
to
330b971
Compare
| Node uses `DefaultPlatform` from `v8:src/libplatform/default-platform.h` which currently simply returns 0. | ||
| A simplistic implementation which logs all trace events to stdout illustrates the basics: | ||
|
|
||
| ```cpp |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
|
The point about the v8 module still appears to be unaddressed. |
| * [LTTng](http://lttng.org/) | ||
| Linux only. | ||
| Some info on using LTTng with Node.js are available in the presentations | ||
| [Tracing Node on Linux with LTTNG](http://nearform.github.io/tracing-node-lttng-nodejsdublin/) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
joshgav
force-pushed
the
foundation
branch
2 times, most recently
from
8138da1
to
4df6d12
Compare
This was referenced May 31, 2016
Closed
|
LGTM |
Add additional top level to repo with subfolders for diagnostic domains. Add initial README.md for each domain. Add some initial docs and samples for domains beyond tracing. Move and minor cleanup of AsyncWrap docs and background info on TRACE_EVENT.
|
Squashed, updated commit message, and fast-forward merged. Thanks all! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is to facilitate transition to a "Diagnostics WG" and to group content by domain. Please review and consider what changes to proposed domains might be needed, and whether to go forward with this transition.
Diagnostic capabilities and tools for Node are in great demand and many of the facilities have overlapping capabilities and consumers, so it seems best to gather and move this all forward in concert.