Your question is Debug Without a Debugger. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
How would you debug a suspected memory leak or stack overflow on an embedded system without a debugger attached?
Explain the practical instrumentation, runtime evidence, and fault-handling strategy you would add to distinguish heap leakage, fragmentation, invalid memory access, and stack exhaustion. Include how you would preserve enough information after a crash to identify the failing task and code path, while keeping the diagnostic changes safe for a resource-constrained target.