Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.20/04
-
None
-
Ubuntu 20.04 LTS / x86_64 / gcc 9.3.0 / Valgrind-3.15.0
Scientific Linux 7.7 / x86_64 / gcc 4.8.5 / Valgrind-3.14.0
Description
Details are here:
https://root-forum.cern.ch/t/valgrind-dies-at-assertion-overlap-failed/38827
It is possible that this is a problem in the valgrind itself ("Valgrind-3.15.0" and "Valgrind-3.14.0" were used).
However, it is also possible that the problem lies in Cling. Assume that there is something "uninitialized" / "improperly initialized" and then, when valgrind tries to "map" it, it dies.
In any case, it really makes debugging problems very difficult.