[Ovmsdev] std::string data corruption (issue #189)

[Michael Balzer]

Everyone please have a look at…

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/189#issuecomment-457334248

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.

Regards,
Michael

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20190124/d9a99969/attachment.html>