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.
+2018-01-19 Andreas Arnez <arnez@linux.vnet.ibm.com>
+
+ * gdb.arch/s390-vregs.exp: Explicitly cast the return values of
+ setrlimit and chdir to int.
+
2018-01-19 Andreas Arnez <arnez@linux.vnet.ibm.com>
* gdb.arch/s390-tdbregs.c (my_tbegin): Add comment documenting the
# directory.
if { $coredir != "" } {
- gdb_test {print setrlimit (4, &(unsigned long [2]){~0UL, ~0UL})} \
+ gdb_test {print (int) setrlimit (4, &(unsigned long [2]){~0UL, ~0UL})} \
" = .*" "setrlimit"
- gdb_test "print chdir (\"${coredir}\")" " = 0" "chdir"
+ gdb_test "print (int) chdir (\"${coredir}\")" " = 0" "chdir"
}
# Initialize all vector registers with GDB "set" commands, using