On Mon, 2018-11-05 at 15:30 -0500, Shahbaz Youssefi wrote: > Looks like I was slightly too quick to ask this question. The issue > seems to be coming from the way LLD produces debugging information, > and adding --no-resegment to LLD fixes the issue: > > https://bugs.chromium.org/p/chromium/issues/detail?id=830706
Note that the above references valgrind bug 384727, duplicate of 395682, which is fixed in valgrind 3.14. So, if you upgrade to latest valgrind release, it should work without --no-resegment. Philippe _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
