Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Johannes Stoelp <Johannes.Stoelp@synopsys.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>,
	 Andreas Ropers <Andreas.Ropers@synopsys.com>,
		Marc Mones <Marc.Mones@synopsys.com>,
		Kai Schuetz <Kai.Schuetz@synopsys.com>
Subject: Re: Infinite Stack Unwinding ARM
Date: Wed, 05 Apr 2017 11:09:00 -0000	[thread overview]
Message-ID: <86pogrp0vj.fsf@gmail.com> (raw)
In-Reply-To: <6ECCE8A0904A1643BE093611EF2098CE0147553E@DE02WEMBXB.internal.synopsys.com>	(Johannes Stoelp's message of "Tue, 4 Apr 2017 12:54:09 +0000")

Johannes Stoelp <Johannes.Stoelp@synopsys.com> writes:

> * Anyone worked on an extension for the prologue analyzer to support SYSRegs and therefore
>   instructions like MRS?

I don't expect prologue analyzer supporting SYSRegs and instruction
MRS.  All the prologue analyzers in GDB are written in a way that
understanding instructions according to the ABI/calling convention of
each architecture and compiler's behavior, so it should be able to parse
the instruction in prologues complying to the ABI.  GDB prologue
analyzer may not understand what does handwritten assembly do.

If you want GDB to unwind from there, add .cfi directives in
arch/arm64/kernel/entry.S

-- 
Yao (齐尧)


  reply	other threads:[~2017-04-05 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 12:54 Johannes Stoelp
2017-04-05 11:09 ` Yao Qi [this message]
2017-04-07  7:15   ` Johannes Stoelp
2017-04-08  5:00     ` Duane Ellis
2017-04-10 12:01     ` Yao Qi
2017-04-11 16:20       ` Johannes Stoelp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86pogrp0vj.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=Andreas.Ropers@synopsys.com \
    --cc=Johannes.Stoelp@synopsys.com \
    --cc=Kai.Schuetz@synopsys.com \
    --cc=Marc.Mones@synopsys.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox