On 12/10/2015 01:11 PM, Philippe Waroquiers wrote: > On Thu, 2015-12-10 at 11:06 -0800, Nikolaus Rath wrote: >> On 12/10/2015 10:20 AM, Matthias Schwarzott wrote: >>> 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. > Oops, yes, I forgot that inline info was not activated for massif tool. > >> >> I am using massif - and bingo, using --read-inline-info=yes makes >> everything work. > This is strange. > --read-inline-info=yes will ensure that e.g. 'v.info scheduler' > stacktraces will show inlined calls, or that 'v.info location <address>' > will describe inlined calls. > > But I do not see how massif output would use it: to be used, > a non NULL iipc argument must be given to VG_(describe_IP). > And massif snapshot does pass NULL (see ms_main.c:2149). > > Are you sure the massif output shows the inlined calls ?
Oh, no, sorry. I was silently assuming that if 'v.info scheduler' produces the correct output, massif would produce the correct output as well. So the answer is then that massif simply does not support inlined calls? Best, -Nikolaus ------------------------------------------------------------------------------ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
