Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: aarch64 regression: gdb.cp/nextoverthrow.exp [Re: [PATCH master+7.12] [AArch64] Match instruction "STP with base register" in prologue]
Date: Tue, 11 Oct 2016 11:25:00 -0000	[thread overview]
Message-ID: <CAH=s-PNEc1v8DEfCOGR_NcmuLkYVQxR2CoWA_1K6t4xBhbHNkA@mail.gmail.com> (raw)
In-Reply-To: <20161010204111.GA25562@host1.jankratochvil.net>

Hi Jan,

On Mon, Oct 10, 2016 at 9:41 PM, Jan Kratochvil
> tbreak _Unwind_RaiseException^M
> aarch64-tdep.c:335: internal-error: CORE_ADDR aarch64_analyze_prologue(gdbarch*, CORE_ADDR, CORE_ADDR, aarch64_prologue_cache*): Assertion `inst.operands[0].type == AARCH64_OPND_Rt' failed.^M
> A problem internal to GDB has been detected,^M
> further debugging may prove unreliable.^M
> Quit this debugging session? (y or n) FAIL: gdb.cp/nextoverthrow.exp: tbreak _Unwind_RaiseException (GDB internal error)
>
> RHEL-7.3-20161007.n.0 Server aarch64
> gcc-4.8.5-11.el7.aarch64
>
> Please contact me (possibly also offlist) if you have it unreproducible.
>

This internal error is caused by instruction "stp with FP registers" in
the prologue.  The instruction triggers this assert is like
"stp d8, d9, [sp, #imm]".  However, aarch64 gdb doesn't track FP registers
at all in prologue analysis.

Could you open a ticket in bugzilla for this error?  I am testing a patch.

-- 
Yao (齐尧)


  reply	other threads:[~2016-10-11 11:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 13:34 [PATCH master+7.12] [AArch64] Match instruction "STP with base register" in prologue Yao Qi
2016-10-10 20:41 ` aarch64 regression: gdb.cp/nextoverthrow.exp [Re: [PATCH master+7.12] [AArch64] Match instruction "STP with base register" in prologue] Jan Kratochvil
2016-10-11 11:25   ` Yao Qi [this message]
2016-10-11 12:40     ` Jan Kratochvil
2016-10-12  8:04       ` Yao Qi

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='CAH=s-PNEc1v8DEfCOGR_NcmuLkYVQxR2CoWA_1K6t4xBhbHNkA@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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