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] S390: Fix infcalls in s390-vregs test case
Date: Fri, 19 Jan 2018 19:19:00 -0000	[thread overview]
Message-ID: <634c1c3109a2ffdf43ef9dab839c88108d9980f3@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 634c1c3109a2ffdf43ef9dab839c88108d9980f3 ***

Author: Andreas Arnez <arnez@linux.vnet.ibm.com>
Branch: master
Commit: 634c1c3109a2ffdf43ef9dab839c88108d9980f3

S390: Fix infcalls in s390-vregs test case

GDB used to assume that functions without debug info return int.  It
accepted an expression containing such a function call and silently
interpreted the function's return value as int.  But nowadays GDB yields
an error message instead, see

  https://sourceware.org/ml/gdb-patches/2017-07/msg00139.html

This affects the s390-vregs test case, because it contains calls to
setrlimit64 and chdir.  When no glibc debug info is installed, these lead
to unnecessary FAILs.  Fix this by adding appropriate casts to the
inferior function calls.

gdb/testsuite/ChangeLog:

	* gdb.arch/s390-vregs.exp: Explicitly cast the return values of
	setrlimit and chdir to int.


             reply	other threads:[~2018-01-19 19:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 19:19 sergiodj+buildbot [this message]
2018-01-19 19:19 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-01-19 21:03 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-01-19 21:07 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-01-19 21:12 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-19 21:15 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-01-19 21:17 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-19 21:18 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-19 21:32 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-19 21:34 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-19 22:03 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-01-20  0:40 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-20 19:36 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-20 20:07 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-20 20:39 ` Failures on Ubuntu-AArch32-m32, " 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=634c1c3109a2ffdf43ef9dab839c88108d9980f3@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).