-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/v5.1] coredump crashes in write_cfg->prepare, 0xa5a5a5a5, COMPILER_STACK_CHECK_MODE_ALL(IDFGH-12169) #13224
Comments
I'll be debugging this further, give me 30 mins |
uh oh. the |
So i added a bunch of logs:
adding the logs solved it somehow |
specificaly, it is these 3 logs that somehow fix the coredump crash. When they're there, the coredump works. When they're not there, it crashes.
|
so! the crash is caused by these kconfigs. afaict, it crashes every time if these kconfigs are set.
I also checked to see whether note: this is my compiler, GCC 12.2.0
|
I wont be debugging this further:
But this is clearly a pretty severe bug somewhere, probably in GCC |
Possibly related issue: Because following flags will increase the stack usage.
|
True, but I've no idea why adding print statements reliably fixes things
|
@chipweinberger Thanks for reporting. I will check it. |
I can reproduce the same issue. Calling I don't have a clear explanation yet. |
any updates? |
Answers checklist.
IDF version.
release/v5.1 (d922d41) (Feb 20, 2024)
Espressif SoC revision.
ESP32-S3 (v0.1)
Operating System used.
macOS
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-S3
Power Supply used.
USB
What is the expected behavior?
I'm simulating a crash using ESP_ERROR_CHECK, I expect a coredump to happen
What is the actual behavior?
The coredump crashes. I think it crashes here
Steps to reproduce.
force a crash by calling _esp_error_check_failed(ESP_ERR_INVALID_RESPONSE, FILE, LINE, __ASSERT_FUNC, #x);
Debug Logs.
More Information.
This is my sdkconfig
The text was updated successfully, but these errors were encountered: