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
Fix misc SOS bugs
* Fix bug in the AddFilesFromDirectoryToTpaList issue: #2596
* Added some logging to GetLineByOffset
* Improve SymbolService.ParseSymbolPath support for Watson. Issue #2512. Can
now handle the various symbol paths that Watson can throw at us. Doesn't support actually calling the symbol server
dll like in the symsrv*symaudit.dll*\\server\share syntax. The dll is ignored.
* Minor doc updates
* Better loadsymbols error message when no server is set
Copy file name to clipboardExpand all lines: documentation/FAQ.md
+2
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
Frequently Asked Questions
2
2
==========================
3
3
4
+
*`dotnet-dump analyze` running on Windows doesn't support MacOS .NET 5.0 and 6.0 core dumps. `dotnet-dump` running on MacOS does support .NET 5.0 but not 6.0 core dumps (which will be fixed in a future dotnet-dump release). MacOS .NET 6.0 core dumps generated by the runtime via [createdump](https://github.com/dotnet/runtime/blob/main/docs/design/coreclr/botr/xplat-minidump-generation.md#os-x) are supported by lldb/SOS running on MacOS.
5
+
4
6
* If SOS or dotnet-dump analyze commands display "UNKNOWN" for types or functions names, your core dump may not have all the managed state. Dumps created with gdb or gcore have this problem. Linux system generated core dumps need the `coredump_filter` for the process to be set to at least 0x3f. See [core](http://man7.org/linux/man-pages/man5/core.5.html) for more information.
5
7
6
8
* If dump collection (`dotnet-dump collect` or `createdump`) doesn't work in a docker container, try adding the SYS\_TRACE capability with --cap-add=SYS\_PTRACE or --privileged.
Copy file name to clipboardExpand all lines: documentation/debugging-coredump.md
+2
Original file line number
Diff line number
Diff line change
@@ -72,6 +72,8 @@ Even if the core dump was not generated on this machine, the native and managed
72
72
73
73
Follow the rest of the above Linux steps to set the symbol server and load native symbols.
74
74
75
+
NOTE: The following issue has been fixed with .NET 6.0 core dumps generated by the runtime (see [createdump](https://github.com/dotnet/runtime/blob/main/docs/design/coreclr/botr/xplat-minidump-generation.md#os-x)) with a recent version of SOS.
76
+
75
77
The MacOS lldb has a bug that prevents SOS clrstack from properly working. Because of this bug SOS can't properly match the lldb native with with the managed thread OSID displayed by `clrthreads`. The `setsostid` command is a work around for this lldb bug. This command maps the OSID from this command:
0 commit comments