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
.NET Monitor is attempting to ingest an update from dotnet/dotnet that has a consistent createdump failure for Linux x64 environments. All tests that involve invoking dump collection over the diagnostic IPC channel are failing for Linux x64.
Dump collection over IPC channel should not unconditionally fail.
Actual behavior
The specific error message from the runtime over the diagnostic IPC channel is:
[createdump] InitializeDAC: GetProcAddress(CLRDataCreateInstance) FAILED Symbol not found: CLRDataCreateInstance
Regression?
This is a regression.
Known Workarounds
Unknown
Configuration
Version: 10.0.0-preview.5.25251.102 from the dotnet/dotnet repository
OS: All Linux distros (namely Alpine 3.20, Debian 12, Ubuntu 20.04, and Azure Linux 3.0)
Architecture: x64
Specific to configuration: Not sure if ARM64 is affected because we don't run that configuration in public PR
Activity
dotnet-policy-service commentedon May 2, 2025
Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.
mikem8361 commentedon May 2, 2025
Looks like the exports (like CLRDataCreateInstance) are not on the DAC binaries. Must be some kind of building problem in the VMR.