aboutsummaryrefslogtreecommitdiff
path: root/bfd/ns32knetbsd.c
diff options
context:
space:
mode:
authorAndreas Arnez <arnez@linux.vnet.ibm.com>2017-07-24 18:35:30 +0200
committerAndreas Arnez <arnez@linux.vnet.ibm.com>2017-07-24 18:35:30 +0200
commit031ed05dd2756557c3f5cda6690a9f3220918ffb (patch)
tree11acc439e083c0b9423c8ad34a3ff929c1fd46c7 /bfd/ns32knetbsd.c
parent7684e58062af4886aceb05ecd83a956bfcd14aaf (diff)
downloadgdb-031ed05dd2756557c3f5cda6690a9f3220918ffb.zip
gdb-031ed05dd2756557c3f5cda6690a9f3220918ffb.tar.gz
gdb-031ed05dd2756557c3f5cda6690a9f3220918ffb.tar.bz2
s390-vregs.exp: Fix Tcl error after non-zero-pad patch
s390-vregs.exp yields a Tcl error: ERROR: can't read "i": no such variable while executing "expr $a_high * ($i + 1) * $a_high " (procedure "hex128" line 2) invoked from within "hex128 $a_high $a_low $b_high $b_low" ... This is a regression, caused by commit 30a254669b16b8 -- "Don't always zero pad in print_*_chars". That patch introduced a new procedure "hex128" for formatting a 128-bit value as hex, but it accidentally moved the calculation of the 128-bit value into that new procedure as well instead of leaving it in the original context. This is fixed. gdb/testsuite/ChangeLog: * gdb.arch/s390-vregs.exp: Calculate parameters to hex128 in the calling context. (hex128): Drop erroneous calculation of parameters.
Diffstat (limited to 'bfd/ns32knetbsd.c')
0 files changed, 0 insertions, 0 deletions