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] Assert on lval_register
Date: Tue, 06 Dec 2016 14:59:00 -0000 [thread overview]
Message-ID: <7c2ba67e6ab10879968c938aefd4d0d0b4ce79bc@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 7c2ba67e6ab10879968c938aefd4d0d0b4ce79bc ***
Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 7c2ba67e6ab10879968c938aefd4d0d0b4ce79bc
Assert on lval_register
This patch adds asserts where the value's lval must be lval_register.
This triggers an error in frame_register_unwind because VALUE_REGNUM
is used but value's lval is not lval_register.
This also reveals a design issue in frame_register_unwind, that is
arguments addrp and realnump are mutually exclusive, we either use
addrp (for lval_memory), or use realnump (for lval_register). This
can be done in a separate patch.
gdb:
2016-12-06 Yao Qi <yao.qi@linaro.org>
* frame.c (frame_register_unwind): Set *realnump if *lvalp is
lval_register.
* value.c (deprecated_value_next_frame_id_hack): Assert
value->lval is lval_register.
(deprecated_value_regnum_hack): Likewise.
next reply other threads:[~2016-12-06 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 14:59 sergiodj+buildbot [this message]
2016-12-06 14:59 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2016-12-06 14:59 ` Failures on Fedora-i686, " sergiodj+buildbot
2016-12-06 15:01 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2016-12-06 15:03 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-12-06 15:05 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2016-12-06 15:13 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-12-06 15:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-12-06 15:15 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-12-06 15:31 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-12-06 15:37 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2016-12-06 16:12 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2016-12-06 16:12 ` Failures on Debian-i686, " sergiodj+buildbot
2016-12-13 4:01 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-12-13 4:19 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-12-13 5:47 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-12-13 6:05 ` Failures on Fedora-ppc64be-native-extended-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=7c2ba67e6ab10879968c938aefd4d0d0b4ce79bc@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).