aboutsummaryrefslogtreecommitdiff
path: root/zlib/trees.h
diff options
context:
space:
mode:
authorSergio Durigan Junior <sergiodj@redhat.com>2015-05-08 13:19:19 -0400
committerSergio Durigan Junior <sergiodj@redhat.com>2015-05-08 13:19:19 -0400
commitf7797074a5dc314f8922d2e90c1a4ea04b189c36 (patch)
treeeeed30c8bd0f4fa887f6e4a331de663bb6e04611 /zlib/trees.h
parent519b5f619baa43f000ad18c079017bea8e7fc06a (diff)
downloadgdb-f7797074a5dc314f8922d2e90c1a4ea04b189c36.zip
gdb-f7797074a5dc314f8922d2e90c1a4ea04b189c36.tar.gz
gdb-f7797074a5dc314f8922d2e90c1a4ea04b189c36.tar.bz2
Fix coredump-filter.exp by correctly unsetting array
In my last commit to make gdb.base/coredump-filter.exp be more robust regarding using arrays in the global namespace, I cleared the "coredump_var_addr" array like this: set coredump_var_addr "" # use coredump_var_addr as an array... This causes DejaGNU to complain because the variable is first set as non-array, and the used as an array. The correct way to do this is to unset the variable using: unset -nocomplain coredump_var_addr # use coredump_var_addr as an array... The "-nocomplain" part is necessary because if the variable doesn't exist "unset" will not error. Tested on Fedora 20 x86_64. gdb/testsuite/ChangeLog: 2015-05-08 Sergio Durigan Junior <sergiodj@redhat.com> * gdb.base/coredump-filter.exp: Correctly unset "coredump_var_addr" array.
Diffstat (limited to 'zlib/trees.h')
0 files changed, 0 insertions, 0 deletions