Hi Dave,
> Also, although your main application clearly has debug information, your
> target file system's libraries may not. Make sure that you have debuginfo
> files in /usr/lib/.debug (default) or /usr/lib/debug. I'm not sure how
> valgrind intercepts the malloc/free calls, but I assume th
Also, although your main application clearly has debug information, your target
file system's libraries may not. Make sure that you have debuginfo files in
/usr/lib/.debug (default) or /usr/lib/debug. I'm not sure how valgrind
intercepts the malloc/free calls, but I assume that valgrind will h
Hi David,
The patch that you site should not be related with the root cause of your
backtrace failure.
The patch can not impact the run-time binaries since it only removes building
some valgrind tests that wouldn't compile in the yocto cross-compilation
environment, as well as some test spec
