You were correct! Somehow my environment setup messed up the configure/build/execution(??) of Valgrind 3.15. It now works correctly with --save-debuginfo=yes ! Thanks ;-)
On Wed, Jul 10, 2019 at 9:25 AM robert somerville <rbrt.somervi...@gmail.com> wrote: > It actually was compiled with debug info ( as noted, Totalview works fine > ). I have tried --keep-debuginfo=yes, but no joy ... > I am investigating whether dlclose was called ... > > On Wed, Jul 10, 2019 at 9:22 AM Tom Hughes <t...@compton.nu> wrote: > >> On 10/07/2019 16:17, Julian Seward wrote: >> > >> > > Valgrind-3.13 (actually I compiled 3.15, but it says 3.13 with >> Valgrind >> > > --version) >> > >> > In that case you're not running the version you compiled. >> > >> > Try running 3.15 and give it the flag --keep-debuginfo=yes. Does that >> > help? >> >> If it was an so that had been unloaded then I don't think it would >> even show the name would it? So I'm not sure --keep-debuginfo=yes >> will help... >> >> Tom >> >> -- >> Tom Hughes (t...@compton.nu) >> http://compton.nu/ >> >
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
