Bin files still contain assert and code strings
Posted: Tue Sep 25, 2018 2:11 am
Hey All,
Trying to get small build binaries, and ultimately byte identical build repeat-ability on different computers, however i am running into some issues.
I have tried to disable all logging, as well as more importantly removing the assert prints using the silent assert mode( and even with assets disabled), However there always still seems to be user readable strings in the built binary.
Eg; the following string can be found in the first 1k of flash in my binaries no matter what options i enable or disable.
As you can see there is still visible user strings in the binary, and more to the point user strings that change depending on where the code is compiled.
Is this a known issue?
Are there any other things that can be done to remove this sort of stuff from the resulting binary?
(Using IDF V3.1)
Trying to get small build binaries, and ultimately byte identical build repeat-ability on different computers, however i am running into some issues.
I have tried to disable all logging, as well as more importantly removing the assert prints using the silent assert mode( and even with assets disabled), However there always still seems to be user readable strings in the built binary.
Eg; the following string can be found in the first 1k of flash in my binaries no matter what options i enable or disable.
Code: Select all
esp_task_wdt_init(CONFIG_TASK_WDT_TIMEOUT_S,.true)./home/lucas/esp32.core/lib/esp-idf/components/esp32/./cpu_start.cIs this a known issue?
Are there any other things that can be done to remove this sort of stuff from the resulting binary?
(Using IDF V3.1)