-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Debugging.md #149
Add Debugging.md #149
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a great starting point, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry I'm late to the party
| path_name_str | `bytes` | Path to debug info file | | ||
|
||
`path_name` is the location of a file containing DWARF debug info. Note that it | ||
may also contain the full wasm file as well, which can be simpler to handle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it might be a little clearer to say that the file with the debug info is a wasm container, and that it might also contain the wasm code.
| Field | Type | Description | | ||
| ------------- | ----------- | ---------------------------------- | | ||
| path_name_len | `varuint32` | Length of `path_name_str` in bytes | | ||
| path_name_str | `bytes` | Path to debug info file | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we specify that this is a relative path (and relative to what?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't have to be relative (I think). Although, instead of path
maybe it would be better to say url
here to make that clearer.
Looks like those should be easy enough to fixup in a follow-up PR? |
See #148