[Bug]: AdvancedLogger Is Not Reentrant Safe in the Init PAth

[os-d]

Is there an existing issue for this?

• I have searched existing issues

Current Behavior

If a debug print occurs in advanced logger's init path, it will enter an infinite loop.

Expected Behavior

We should be a bit more "advanced." After permanent memory is installed is when this is an issue, we can use a module global to check if we are already in AdvLogger at that point.

Steps To Reproduce

Hit a debug statement in adv logger init path.

Build Environment

- OS(s):
- Tool Chain(s):
- Targets Impacted:
All.

Version Information

top of tree.

Urgency

Medium

Are you going to fix this?

I will fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

[github-actions]

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

[github-actions]

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.