Native frames missing crashreport.json

[kdubau]

Description

The crashreport.json file seems to be missing all native frames up until the first managed frame, except for the very first one, which is missing the unmanaged_name field.

Reproduction Steps

Enabled the core dump, and the crash report, and induce a crash. Compare the json with what you see in LLDB with clrstack -f.

Expected behavior

All stack frames should be in the json report.

Actual behavior

Missing frames.

Regression?

Yes, introduced with this PR #60995

Known Workarounds

None

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

The crashreport.json file seems to be missing all native frames up until the first managed frame, except for the very first one, which is missing the unmanaged_name field.

Reproduction Steps

Enabled the core dump, and the crash report, and induce a crash. Compare the json with what you see in LLDB with clrstack -f.

Expected behavior

All stack frames should be in the json report.

Actual behavior

Missing frames.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author:	kdubau
Assignees:	mikem8361
Labels:	area-Diagnostics-coreclr
Milestone:	6.0.x

[kdubau]

@mikem8361 I also just noticed, if you look at the first frame in the json, it's tagged "is_managed": "true" but it's a native frame.