microsoft / microsoft/mu_basecore

[Feature]: Support Printing Stack Dump From Assert

Open
#560 0 comments 0 reactions 1 assignee View on GitHub

@os-d is already working on this.

Since Sep 11, 2023.

state:backlog state:needs-triage type:feature-request urgency:medium
Dominant language
C
Stars
290
Forks
187
Avg merge
1d 7h
Merged PRs (30d)
37

Description

### Feature Overview

Today, there is no option to support dumping the stack when an assert is triggered. However, this is extremely useful, particularly when an assert is hit in core code (for example on a pool free) so that the faulty component can be identified without needing to attempt a repro, improving the debugability.

### Solution Overview

An additional bit can be added to PcdDebugPropertyMask to instruct the core code to dump the stack and related information (similar as occurs on an exception).

This depends on issue #559 to split assert functionality out of DebugLib. It could go in before, but makes sense to define that interface first.

### Alternatives Considered

_No response_

### Urgency

Medium

### Are you going to implement the feature request?

I will implement the feature

### Do you need maintainer feedback?

No maintainer feedback needed

### Anything else?

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.