Re: [PATCH 3/3] tools/perf/jvmti: generate correct debug information for inlined code

[Ben Gainey]

On Wed, 2017-11-29 at 05:02 -0800, Stephane Eranian wrote:
> On Thu, Nov 23, 2017 at 7:22 AM, Arnaldo Carvalho de Melo
> <acme@xxxxxxxxxx> wrote:
> >
> > Em Wed, Nov 22, 2017 at 06:25:41PM -0600, Kim Phillips escreveu:
> > > From: Ben Gainey <ben.gainey@xxxxxxx>
> > > @@ -405,7 +405,9 @@ jvmti_write_debug_info(void *agent, uint64_t
> > > code, const char *file,
> > >               return -1;
> > >       }
> > >
> > > -     flen = strlen(file) + 1;
> > > +     for (i = 0; i < nr_lines; ++i) {
> > > +         flen += strlen(file_names[i]) + 1;
> > > +     }
> >
> >
> > Please follow the coding standard used in this file and in
> > tools/perf,
> > which is the kernel one.
> >
> > Thanks for providing instructions on how to reproduce the problem!
> >
> > Stephane, can you please Ack this?
> >
>
> Trying to test this but do not see the source code from example, yet.

Hi Stephane, sorry can you please clarify; were you expecting to see
source embedded in the output from perf annotate, or are just missing
the source for the reproducer, or something else?

If it is the former, then there is no source in the output, only line
numbers and filenames, but this is not a regression (that I am aware
of) as it was not there before the patch either.


>
> >
> > - Arnaldo
>
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.