-
Notifications
You must be signed in to change notification settings - Fork 19
Add basic GDB remote protocol encoding/decoding #204
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
base: main
Are you sure you want to change the base?
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.
Added separate Package.swift
manifest to hide debugger support behind a trait for now, and traits aren't supported in 6.0.
.target(name: "GDBRemoteProtocol", | ||
dependencies: [ | ||
.product(name: "NIOCore", package: "swift-nio"), | ||
] | ||
), | ||
.testTarget(name: "GDBRemoteProtocolTests", dependencies: ["GDBRemoteProtocol"]), |
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.
These two modules are meant to be completely independent of WasmKit and in the future could live in a separate package to be adopted in any suitable environment that needs debugging facilities, not just Wasm.
c6bb762
to
e2be1c7
Compare
qWasmCallStack
qWasmCallStack
qWasmCallStack
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.
What do you think about landing the GDBRemoteProtocol module to the main branch first, then land the remaining engine changes?
I'd like to review the engine changes carefully not to regress performance and spec compliant, so splitting them would help me a lot 🙏
35bc821
to
2d065e0
Compare
fed04da
to
17f9d5f
Compare
17f9d5f
to
16ac0cf
Compare
qWasmCallStack
See GDB and LLDB remote protocol documentation for more details: