[Ovmsdev] std::string data corruption (issue #189)
dexter at expeedo.de
Tue Jan 29 03:43:01 HKT 2019
For those not following the github discussion: I'm pretty sure I've nailed the bug down.
I have reproduced the bug in a simple test project and intend to raise an issue with Espressif on this.
If you'd like to test this on your module, configure the project to your wifi credentials, then use "make flash". As the test project is small, this normally
will not erase your OVMS config partition, but a backup is always recommended.
Am 24.01.19 um 21:19 schrieb Michael Balzer:
> Everyone please have a look at…
> Please try to reproduce the bug on your modules.
> I'm open for explanations.
> I thought this might be some copy-on-write bug with std::string, but the gcc 5.x libstdc++ does no longer use that implementation (wouldn't be C++11 compliant
> as well). I also tried moving all strings to temporary buffers, but modes 5 & 6 eliminated this explanation as well.
> My remaining theories:
> * A task writing out of bounds (but only 0-bytes?)
> * A hardware issue only affecting some modules
> A hardware issue only affecting some percentage of ESP32 could explain this as well as the strange heap corruptions that seem to affect some modules
> especially often.
> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OvmsDev