-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Open
Labels
Description
Issue description
In former versions of dotnet-dump analyze I where able to search for types in the heap by typing dumpheap -T xxxxx. I setup a new dotnet project for playing around with diagnostics stuff and used RUN dotnet-install dotnet-dump in the Dockerfile. In the container I tried to analyze a dump. dumpheap -T xxx gave me this error:
System.ArgumentException: Invalid start address: -T
I took a look into the help and saw:
dumpheap <memoryrange> Displays a list of all managed objects.
But the official documentation says:
dumpheap | Displays info about the garbage-collected heap and collection statistics about objects.
Can you please fix the documentation and tell me how I can achieve the type filtering with the new version?
Target framework
- [x ] .NET Core 6.0.414
- .NET Framework
- .NET Standard
.NET SDK (reflecting any global.json):
Version: 6.0.414
Commit: dc3b5c4341
Runtime Environment:
OS Name: debian
OS Version: 11
OS Platform: Linux
RID: debian.11-x64
Base Path: /usr/share/dotnet/sdk/6.0.414/
global.json file:
Not found
Host:
Version: 6.0.22
Architecture: x64
Commit: 4bb6dc195c
.NET SDKs installed:
6.0.414 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.22 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.22 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 9a269a64-0a27-27d3-a509-47b9a0d114bf
- Version Independent ID: 49ff97ff-b39a-5ae8-e4b8-81a4f8eab50c
- Content: dotnet-dump diagnostic tool - .NET CLI - .NET
- Content Source: docs/core/diagnostics/dotnet-dump.md
- Product: dotnet-fundamentals
- GitHub Login: @tommcdon
- Microsoft Alias: tommcdon