[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170619185939.GA2170@redhat.com>
Date: Mon, 19 Jun 2017 15:59:39 -0300
From: Arnaldo Carvalho de Melo <acme@...hat.com>
To: Milian Wolff <milian.wolff@...b.com>
Cc: Jan Kratochvil <jan.kratochvil@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
"linux-kernel@...r.kernel.org" <Linux-kernel@...r.kernel.org>,
linux-perf-users <linux-perf-users@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Yao Jin <yao.jin@...ux.intel.com>, Jiri Olsa <jolsa@...hat.com>
Subject: Re: perf report: fix off-by-one for non-activation frames
Em Sat, Jun 17, 2017 at 01:13:11PM +0200, Milian Wolff escreveu:
> On Samstag, 17. Juni 2017 10:04:02 CEST Jan Kratochvil wrote:
> > On Sat, 17 Jun 2017 09:56:57 +0200, Namhyung Kim wrote:
> > > Not sure whether it needs be fixed or not. If we fix it, srcline and
> > > address would not match so it can give its own confusion to users.
> > > Ideally it should display an addressof the instruction before the
> > > address IMHO.
> >
> > One can figure million ways how it can behave and each one has its pros and
> > cons. I was just describing the current behavior of GDB and LLDB which
> > people are used to already.
>
> Personally, I agree with Jan that we should mimick existing tool's behavior. I
> just fear that it's not trivial to do it with the current code base...
But we agree it is a worthwhile change (have backtraces in perf match
what gdb, etc show), right?
If you can, please try to do this, your attempt will help us understand
more the extent of the changes needed and perhaps someonw can come up
with simplifications...
- Arnaldo
Powered by blists - more mailing lists