public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] ARM process record: VMOV
Date: Fri, 04 Mar 2016 17:01:00 -0000	[thread overview]
Message-ID: <f1771dcebf80c75a13ca456491ddfb9b43fcaddf@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT f1771dcebf80c75a13ca456491ddfb9b43fcaddf ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: f1771dcebf80c75a13ca456491ddfb9b43fcaddf

ARM process record: VMOV

ARM process record gets the wrong register number for VMOV (from core
register to single-precision register).  That is, we should record
the D register rather than the S pseudo register.  The patch also
removes the condition "bit (arm_insn_r->arm_insn, 20)" check, which
has been checked above.

It fixes the following internal error,

(gdb) PASS: gdb.reverse/finish-precsave.exp: BP at end of main
continue^M
Continuing.^M
../../binutils-gdb/gdb/regcache.c:649: internal-error: regcache_raw_read: Assertion `regnum >= 0 && regnum < regcache->descr->nr_raw_registers' failed.^M
A problem internal to GDB has been detected,FAIL: gdb.reverse/finish-precsave.exp: run to end of main (GDB internal error)

gdb:

2016-03-04  Yao Qi  <yao.qi@linaro.org>

	* arm-tdep.c (arm_record_vdata_transfer_insn): Simplify the
	condition check.  Record the right D register number.


             reply	other threads:[~2016-03-04 17:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 17:01 sergiodj+buildbot [this message]
2016-03-04 17:02 ` Failures on AIX-POWER7-plain, branch master sergiodj+buildbot
2016-03-04 17:37 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-03-04 17:40 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-03-04 17:43 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-03-04 17:45 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-03-04 18:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-04 18:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-03-04 18:32 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-04 18:36 ` Failures on Debian-i686, " sergiodj+buildbot
2016-03-04 18:57 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-03-04 19:08 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-03-04 19:25 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-03-04 19:33 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-03-04 19:46 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-03-04 19:48 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2016-03-04 20:08 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-04 20:35 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-03-04 20:55 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-03-04 21:14 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-03-04 22:31 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot

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=f1771dcebf80c75a13ca456491ddfb9b43fcaddf@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).