Am 09.12.2015 um 22:10 schrieb Nikolaus Rath: > > Yes. But that makes it even more confusing to me: apparently gdb picks > up the debug information about the inlined function just fine - but > valgrind doesn't. > > > I'll update valgrind to most recent and see if I can explicitly disable > inlining. > > Do you do your experiments with massif or with memcheck?
If it is massif then read-inline-info defaults to "no". an explicit --read-inline-info=yes could at least make valgrind core save the extra information. But I do not know if massif will care about this information. Regards Matthias ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
