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
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
I just realized that when CONFIG_ESP_SYSTEM_PANIC_GDBSTUB is checked (Under Component config → ESP System Settings → Panic handler behaviour) the core-dump-to-flash did not generate any data.
github-actionsbot
changed the title
CONFIG_ESP_SYSTEM_PANIC_GDBSTUB suppress CONFIG_ESP_COREDUMP_ENABLE in panic.c but the menuconfig does not specify the conflict
CONFIG_ESP_SYSTEM_PANIC_GDBSTUB suppress CONFIG_ESP_COREDUMP_ENABLE in panic.c but the menuconfig does not specify the conflict (IDFGH-8567)
Oct 20, 2022
Actually, I cant think of a good reason why you shouldnt be allowed to use both. We have merged an internal MR to allow these features to be used together now.
espressif-bot
pushed a commit
to espressif/esp-hal-components
that referenced
this issue
Feb 21, 2023
Answers checklist.
General issue report
I just realized that when CONFIG_ESP_SYSTEM_PANIC_GDBSTUB is checked (Under
Component config → ESP System Settings → Panic handler behaviour
) the core-dump-to-flash did not generate any data.esp-idf/components/esp_system/panic.c
Lines 348 to 349 in e9d7340
Clearly, core dump is not enabled when GDB Stub is in use. I think those two options should be linked with Kconfig dependencies.
The text was updated successfully, but these errors were encountered: