mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
a91de43537
Previous version used exception handling for program control flow, which makes for long and confusing backtrace messages if an error occurs while parsing the CSV (as it also prints the phony error that occurred while trying to parse as a binary, then prints "During handling of the above exception, another exception occurred:", then prints the real error). Use the same heuristic that is applied in gen_esp32_part, instead. Also, avoid printing the entire backtrace if the error is a gen_esp32_part InputError, same as gen_esp32part does. Found while looking into https://github.com/espressif/esp-idf/issues/4474 |
||
|---|---|---|
| .. | ||
| test | ||
| test_gen_esp32part_host | ||
| CMakeLists.txt | ||
| component.mk | ||
| gen_empty_partition.py | ||
| gen_esp32part.py | ||
| Kconfig.projbuild | ||
| Makefile.projbuild | ||
| partitions_singleapp_coredump.csv | ||
| partitions_singleapp.csv | ||
| partitions_two_ota_coredump.csv | ||
| partitions_two_ota.csv | ||
| parttool.py | ||
| project_include.cmake | ||