Rename variable "addr" to "coredump_var_addr" in gdb.base/coredump-filter.exp
authorSergio Durigan Junior <sergiodj@redhat.com>
Mon, 13 Apr 2015 06:40:08 +0000 (02:40 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Mon, 13 Apr 2015 06:45:16 +0000 (02:45 -0400)
commit8cd8f2f8ac49276437b7da37f275706ea1c1c925
treefc286716e21422b80752ae87fb80869dc463c2c7
parentbf12d44ee075e694a2b0dca87b9e9ca0e685d319
Rename variable "addr" to "coredump_var_addr" in gdb.base/coredump-filter.exp

This commit renames the global array variable "addr" to an unique name
"coredump_var_addr" in the test gdb.base/coredump-filter.exp.  This is
needed because global arrays can have name conflicts between tests.
For example, this specific test was conflicting with dmsym.exp,
causing errors like:

  ERROR: tcl error sourcing ../../../../../binutils-gdb/gdb/testsuite/gdb.base/dmsym.exp.
  ERROR: can't set "addr": variable is array
      while executing
  "set addr "0x\[0-9a-zA-Z\]+""
      (file "../../../../../binutils-gdb/gdb/testsuite/gdb.base/dmsym.exp" line 45)
      invoked from within
  "source ../../../../../binutils-gdb/gdb/testsuite/gdb.base/dmsym.exp"
      ("uplevel" body line 1)
      invoked from within
  "uplevel #0 source ../../../../../binutils-gdb/gdb/testsuite/gdb.base/dmsym.exp"
      invoked from within
  "catch "uplevel #0 source $test_file_name""

This problem was reported by Yao Qi at:

  <https://sourceware.org/ml/gdb-patches/2015-04/msg00373.html>
  Message-Id: <1428666671-12926-1-git-send-email-qiyaoltc@gmail.com>

gdb/testsuite/ChangeLog:
2015-04-13  Sergio Durigan Junior  <sergiodj@redhat.com>

* gdb.base/coredump-filter.exp: Rename variable "addr" to
"coredump_var_addr" to avoid naming conflict with other testcases.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/coredump-filter.exp
This page took 0.026256 seconds and 4 git commands to generate.