Hi,
I'm in the following situation and need help understanding why
valgrind doesn't show debug symbols. First of all, I'm on Linux 4.15
x86_64, valgrind 3.13.0. I'm running valgrind on ANGLE
(angleproject.org). Normally, this library provides a .so file that I
believe gets dynamically loaded, but
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
On Mon, Nov 5, 2018 at 3:24 PM Shahbaz Youssefi wr
On Sun, 2018-11-04 at 20:36 -0800, John Reiser wrote:
> > What techniques can we employ to speed things up (whilst retaining most of
> > the value)?
> The memcheck option --expensive-definedness-checks= already defaults to 'no'.
Note that it defaults to 'auto' in 3.14.
> Specifying --redzone-siz
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
Thanks for the replies...
Tweaking the optimization settings did very little for the running time.
However a huge difference (factor of 2) comes from taking out
--show-reachable=yes --track-origins=yes except they are very very
useful... so I sort of don't want to.
On Tue, Nov 6, 2018 at 9:43 A
