Hi, This became rather lengthy, please bear with me. Assuming Heap Debugging is set to "Comprehensive", when allocating a block of memory (multi_heap_malloc()), an additional poison_head_t and poison_tail_t are allocated. Then, it goes on to poison the allocated buffer in poison_allocated_region(), ...

Usually 10k are sufficient, though it depends what will be pulling them down if that is ever a use case in your setup. I'd check some reference drawings.

Hi, Anyone managed to get Coverity to accept your project? When running cov-build all I get is: [WARNING] No files were emitted. This may be due to a problem with your configuration The build process completes like it always do. I ran Coverity as follows: make clean cov-configure --compiler /home/pe...

I'm so glad that you asked this question. I've been looking for a solution like this and now I have one. Thanks Vader_Mester!

For those who don't frequent GitHub, I've posted an issue/query regarding -fsanitize and code quality in general: https://github.com/espressif/esp-idf/issues/1574 If you agree with my thinking, please give it a thumbs up to tell Espressif this is something the community wants.

permal wrote:Btw, does -fsanitze work with xtensa-gcc?

Sadly, it does not

Btw, does -fsanitze work with xtensa-gcc?

I have the old copy on disk still and will do comparative tests this evening. As the corruption currently happens fairly quickly it should be pretty easy to determine if there is a difference.

Hi, I've had this code that has been running for days without interruption, but after updating ESP-IDF and the tool chain I'm getting crashes with stack traces like the those below. I am well aware that this might very well be something that has been latent in my own code and I'm not pointing finger...

But do they actually sell them, I can't find the ESP32-PICO-D4 in the shop?

So far only Electrodragon seems to actually have them.

@Espressif - care to help us out with a list of stores that sells the ESP32-PICO-D4?