You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: Don't print stack trace to Serial on crash #9194
I have read the documentation at readthedocs and the issue is not addressed there.
I have tested that the issue is present in current master branch (aka latest git).
I have searched the issue tracker for a similar issue.
[N/A] If there is a stack dump, I have decoded it.
I have filled out all fields below.
Platform
Hardware: ESP8266
Core Version: 3.1.2 (latest)
Development Env: VS Code + Microsoft Arduino Extension
Operating System: Windows
Settings in IDE
Module: Generic ESP8266 Module
Problem Description
Hi there, I'm trying to change the behavior of the postmortem_report() call not to print anything to the Serial upon a crash. The serial port in question is connected to a peripherical and is not used for debugging purposes.
So far, my efforts in #9193 have been unsuccessful. I am unable to override the postmortem_report() call via my code.
This got me thinking, can you possibly please introduce a new flag that would prevent the default function from being defined, or avoid printing to the serial? Currently the custom_crash_callback() callback is called after the postmortem_report() has finished printing to the Serial port.
Activity
DRSDavidSoft commentedon Aug 29, 2024
It would be awesome if we could somehow override
postmortem_report()completely.DRSDavidSoft commentedon Aug 17, 2025
@mcspr, I would like to discuss implementing a way for the user to override
postmortem_report(), which would make certain parts of #9196 unnecessary.Could you please share your opinion on this?
Postmortem - export user reset reason & extra callbacks
mcspr commentedon Aug 27, 2025
See #9271
If you had a different idea for implementation, please share :) No need to ask me first