-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Remove SOS and lldb plugin from the coreclr repo #12524
Comments
Does this mean an SOS built out of the coreclr repo is going to ship in 3.0? If so, I want to port from the diagnostics repo some changes that were made only there when it was stated that SOS would not ship out of dotnet/coreclr in 3.0. |
I still won't bother with merging the changes into coreclr. The diagnostics repo SOS has a lot of new features and fixes that coreclr doesn't. I need to discuss this with Tom, but I still do want to remove SOS from coreclr in the Preview 7 timeframe otherwise it will probably ship with 3.0. |
SOS is ready to remove from the runtime/coreclr repo when:
|
@mikem8361 I've moved the issue back to 3.0. Thanks for putting together the release checklist! |
* Remove SOS and lldb plugin Issue: https://github.com/dotnet/coreclr/issues/24092
* Remove SOS and lldb plugin Issue: https://github.com/dotnet/coreclr/issues/24092
SOS and the lldb plugin now live in the diagnostics repo. We are almost ready to remove them from the coreclr repo probably in the Preview 6 time frame.
We are still waiting for the new SOS to shipping with the next public release of the Windows debugger (windbg) and there are still some OS/architecture holes in the diagnostics repo's build (and test) matrix (i.e. arm, arm64, FreeBSD, etc.).
The text was updated successfully, but these errors were encountered: