Skip to content
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

Wrap in WinDbg extension #15

Open
goldshtn opened this issue Jul 12, 2015 · 3 comments
Open

Wrap in WinDbg extension #15

goldshtn opened this issue Jul 12, 2015 · 3 comments

Comments

@goldshtn
Copy link
Owner

Could be something very simple that just forwards any arguments to msos. For example:

> !msos !dumpheap --stat

Need to figure out how to let ClrMD connect to the same target. Maybe by initializing DataTarget around WinDbg's IDebugInterface? Or maybe just opening another one with the ClrMD engine?

@goldshtn
Copy link
Owner Author

There's also the issue of interpreting arguments and escaping. For example, we probably want @$tn variables to be available as part of the command, so we don't want !msos to eat them. Similarly, what happens to quotes, semicolons, WinDbg keywords, etc.

@goldshtn
Copy link
Owner Author

DataTarget can be created from IDebugClient, so no worries there.

@goldshtn goldshtn self-assigned this Aug 25, 2015
@goldshtn
Copy link
Owner Author

Some work started in windbg-extension branch, but a lot still remaining. Among other things, split .exe into msoscore.dll and msos.exe. Need msoscore.dll to use Costura and pack itself up into a single file as well, for compactness (question is whether the unmanaged deps like symsrv.dll remain in the .exe?). Also need some code to create an AnalysisTarget out of IDebugClient passed from the extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant