>> is it certain, based on what you've seen, that I actually am using the debug >> package? I installed it, which apparently is all that is required to cause >> it to get used when compiled for debugging?
> There is a chance of pathname mixup: installing into the "wrong" directory. > > The way to tell is to run valgrind under strace: > > $ strace -f -o strace.out -e trace=file ~/local/bin/valgrind > --leak-check=yes ./clock_gettime CLOCK_MONOTONIC > > and afterwards look in strace.out for any open() on the debug symbol file(s). > Also try $ ~/local/bin/valgrind -d -d -d -v -v -v --leak-check=yes ./clock_gettime CLOCK_MONOTONIC and look for debug symbol loading such as: ----- --25057:1:main Load initial debug info --25057-- Reading syms from /usr/bin/date --25057-- svma 0x0000401ad0, avma 0x0000401ad0 --25057-- Considering /usr/lib/debug/.build-id/08/884e015589393715fa4c5d3e9a4ab0d1541e99.debug .. --25057-- .. build-id is valid ----- -- ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
