Skip to content

createdump fails to collect actionable dumps on macOS 13 Ventura  #79355

Description

@tommcdon

Description

We have had a partner team as well as other internal reports that crashreport.json files contain empty stacks and MachO dumps collected on macOS 13 Ventura do not contain valid callstacks or exception information. .NET dumps are needed to collect actionable crash and hang report information for processes. This bug blocks collecting both crash dump reports as well as actionable crash reports.

Reproduction Steps

  1. Install .NET 6 or .NET 7 on macOS 13 Ventura
  2. Either collect a dump using the crash dump and report environment variables or trigger a dump using dotnet-dump
  3. Use dotnet-dump analyze to view callstacks int he dump.
  4. Observe empty callstacks in the collected dump.

Expected behavior

.NET dumps and crash reports on macOS 13 Ventura contain valid information

Actual behavior

Createdump will output the error InitalizeDAC: coreclr not found; not using DAC. Callstacks in the crashreport.json as well as dotnet-dump analyze output are empty.

Regression?

This is a regression when upgrading to macOS 13 Ventura

Known Workarounds

No known workaround

Configuration

.NET versions: .NET 6 and 7
OS: macOS 13 Ventura
Architecture: x64, arm64

Other information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions