Dave,
When I looked at the output from "bt -f" command, I found that stack dump
starts from frame.sp in arm64_print_stackframe_entry().
Usage of stack frames on arm64 is a bit different from that on x86, and
using frame.fp is, I believe, much useful (and accurate) for crash users.
See my patch att
On Tue, Jun 07, 2016 at 03:01:49PM -0400, Dave Anderson wrote:
>
> And a fix for the phantom exception frame issue has been checked in:
>
>
> https://github.com/crash-utility/crash/commit/14b3eadfd8cfafa19115c06aa4e52a8d23f823cf
>
> Fix for the ARM64 "bt" command in Linux 4.5 and later kern
On Tue, Jun 07, 2016 at 03:50:12PM -0400, Dave Anderson wrote:
>
> - Original Message -
> >
> >
> > - Original Message -
> > > On Wed, Jun 01, 2016 at 10:32:56AM -0400, Dave Anderson wrote:
> > > >
> > > > - Original Message -
> > > > > On Tue, May 31, 2016 at 03:30:44PM
- Original Message -
>
>
> - Original Message -
> > On Wed, Jun 01, 2016 at 10:32:56AM -0400, Dave Anderson wrote:
> > >
> > > - Original Message -
> > > > On Tue, May 31, 2016 at 03:30:44PM -0400, Dave Anderson wrote:
> > > > >
> > > > > This patch looks good -- if it
And a fix for the phantom exception frame issue has been checked in:
https://github.com/crash-utility/crash/commit/14b3eadfd8cfafa19115c06aa4e52a8d23f823cf
Fix for the ARM64 "bt" command in Linux 4.5 and later kernels which
are not configured with CONFIG_FUNCTION_GRAPH_TRACER. Without th
Hello Takahiro,
I went ahead and checked in a fix for the user-space backtrace issue here:
https://github.com/crash-utility/crash/commit/2d53b97a476e71bfd5e2054d64aacfc5fd895e30
Fix for the ARM64 "bt" command in Linux 4.5 and later kernels which
use per-cpu IRQ stacks. Without the pa
