You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copilot aided release notes for user facing changes
---------------------------------------------------------------------
Breaking Changes
- COMPLUS_* environment variable references removed from SOS — use
DOTNET_* equivalents (#5714)
- !name2ee and !token2ee output is now less verbose; modules that don't
contain the requested type are no longer listed (#5719)
dotnet-dump / SOS
New features:
- Add -stat flag to !threadpool to summarize queued work items by type
(#5737)
- Add sort-by-count option to !dumpheap (#5722)
- Add -noprogress flag to !dumpheap and !verifyheap to suppress progress
reporting (#5773)
- Add -all flag to DumpMT to show class details and method descriptors
in one command (#5701)
- !DumpStackObjects now finds objects correctly during stack overflow
scenarios on Linux (#5723)
- Warn when loading a dump not collected by createdump, as SOS commands
may produce incomplete results (#5720)
- SOS output is now captured correctly by LLDB Python scripts and tools
like lldb-dap (#5728)
Bug fixes:
- Fix !u failing on IL stubs (#5726)
- Fix DumpIL showing a cryptic error on IL stubs — now explains IL is
unavailable (#5731)
- Fix clrstack -l displaying incorrect values for ushort locals ≥ 0x8000
(#5721)
dotnet-trace / collect-linux
- Enable callstack capture for .NET runtime events in collect-linux —
exception and GC stacks now include resolved frames (#5756)
- collect-linux --probe now gracefully handles unreachable processes
instead of throwing (#5705)
- Fix crash in collect-linux in environments without terminal cursor
support (#5771)
- Fix collect-linux throwing when stdin/stdout are redirected (e.g.
piped or scripted) (#5745)
- Fix terminal cursor not being restored after collect-linux exits
(#5747, #5707)
dotnet-counters
- Add --noAbbreviateValues option to monitor to display full-precision
values without K/M/G abbreviation (#5734)
Diagnostic Tools (general)
- Fix WriteDump failing when the dump path contains spaces on Windows
(#5593)
- Diagnostic tools now work from sidecar containers — dotnet-trace,
dotnet-counters, dotnet-stack, and dotnet-dump can attach to processes
in other containers without manual socket configuration (#5735)
Libraries
- Improved symbol resolution performance by caching failed lookups
(#5729)
- Symbol server key generation now supports ELF binaries from custom
toolchains (#5736)
Copy file name to clipboardExpand all lines: documentation/FAQ.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ Frequently Asked Questions
73
73
74
74
If that doesn't work, try using the `setclrpath <directory>` command with a directory that contains the matching version of the DAC module. This is useful for private runtimes or debug builds that haven't been published to our symbol servers.
75
75
76
-
If this is a dump, the problem could also be that the dump is missing some memory required by SOS. Try generating a "full" dump (the default with `dotnet-dump collect` without a `--type` option) or add setting the crash dump generation (createdump) environment variable `DOTNET_DbgMiniDumpType=4` (.NET 6 and below require `COMPlus_` prefix instead of `DOTNET_`). For more details on crash dump generation see [here](https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dumps#collecting-dumps-on-crash).
76
+
If this is a dump, the problem could also be that the dump is missing some memory required by SOS. Try generating a "full" dump (the default with `dotnet-dump collect` without a `--type` option) or add setting the crash dump generation (createdump) environment variable `DOTNET_DbgMiniDumpType=4`. For more details on crash dump generation see [here](https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dumps#collecting-dumps-on-crash).
77
77
78
78
* If you receive this error message executing a SOS command:
0 commit comments