From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [testsuite patch] Skip py-unwind.exp on x86_64 -m32
Date: Sun, 17 Jul 2016 14:30:00 -0000 [thread overview]
Message-ID: <20160717143003.GA12147@host1.jankratochvil.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Hi,
(gdb) source /home/jkratoch/redhat/gdb-clean/gdb/testsuite/outputs/gdb.python/py-unwind/py-unwind.py^M
Python script imported^M
Python Exception <type 'exceptions.ValueError'> Bad register: ^M
(gdb) FAIL: gdb.python/py-unwind.exp: import python scripts
class TestUnwinder(Unwinder):
AMD64_RBP = 6
AMD64_RSP = 7
AMD64_RIP = 16
This was already discussed here:
Re: [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32
https://sourceware.org/ml/gdb-patches/2016-04/msg00222.html
Message-ID: <20160411195537.GA22299@host1.jankratochvil.net>
but no GDB maintainer gave an answer how to run testsuite in cross-arch mode.
Jan
[-- Attachment #2: 1 --]
[-- Type: text/plain, Size: 680 bytes --]
gdb/testsuite/ChangeLog
2016-07-17 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.python/py-unwind.exp: Test also ![is_lp64_target].
diff --git a/gdb/testsuite/gdb.python/py-unwind.exp b/gdb/testsuite/gdb.python/py-unwind.exp
index 5172a03..e31a472 100644
--- a/gdb/testsuite/gdb.python/py-unwind.exp
+++ b/gdb/testsuite/gdb.python/py-unwind.exp
@@ -28,7 +28,7 @@ if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile}] } {
if { [skip_python_tests] } { continue }
# This test runs on a specific platform.
-if { ! [istarget x86_64-*]} { continue }
+if { ![istarget x86_64-*-* ] || ![is_lp64_target] } { continue }
# The following tests require execution.
next reply other threads:[~2016-07-17 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 14:30 Jan Kratochvil [this message]
2016-07-18 10:04 ` Yao Qi
2016-07-18 11:34 ` Jan Kratochvil
2016-07-19 10:06 ` Yao Qi
2016-07-19 18:04 ` Pedro Alves
2016-07-20 11:20 ` Yao Qi
2016-07-20 13:49 ` Pedro Alves
2016-07-20 14:19 ` [commit] " Jan Kratochvil
2016-07-19 19:30 ` Sergio Durigan Junior
2016-07-20 13:48 ` Pedro Alves
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=20160717143003.GA12147@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@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).