diff options
author | Pedro Alves <palves@redhat.com> | 2010-04-01 00:55:03 +0000 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2010-04-01 00:55:03 +0000 |
commit | 0db9b91c94a19133307e24644b54bbad1f1c0033 (patch) | |
tree | 5f30debc95aefe2872b6a370674cca0e874d2597 /gdb/testsuite/gdb.trace/collection.exp | |
parent | dde5d5bf855a9e4036ccd6d0a0095856ef3af5cb (diff) | |
download | gdb-0db9b91c94a19133307e24644b54bbad1f1c0033.zip gdb-0db9b91c94a19133307e24644b54bbad1f1c0033.tar.gz gdb-0db9b91c94a19133307e24644b54bbad1f1c0033.tar.bz2 |
* gdb.trace/collection.exp (gdb_collect_args_test)
(gdb_collect_argarray_test): XFAIL the tests that assume the
argarray argument's elements are collected.
Diffstat (limited to 'gdb/testsuite/gdb.trace/collection.exp')
-rw-r--r-- | gdb/testsuite/gdb.trace/collection.exp | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.trace/collection.exp b/gdb/testsuite/gdb.trace/collection.exp index 5d510ab..986cfaf 100644 --- a/gdb/testsuite/gdb.trace/collection.exp +++ b/gdb/testsuite/gdb.trace/collection.exp @@ -166,15 +166,30 @@ proc gdb_collect_args_test { myargs msg } { "collect $msg: collected arg struct member double" # array arg as one of several args (near end of list) + + # It isn't clear why is the test assuming the array's elements are + # collected. In C, an array as function parameters is a special + # case; it's just a pointer into the caller's array, and as such, + # that's what normally the debug info describes. Maybe this was + # originaly written for a compiler where array parameters were + # really described as arrays in debug info. + + setup_xfail "*-*-*" gdb_test "print argarray\[0\]" \ "\\$\[0-9\]+ = 111$cr" \ "collect $msg: collected argarray #0" + + setup_xfail "*-*-*" gdb_test "print argarray\[1\]" \ "\\$\[0-9\]+ = 112$cr" \ "collect $msg: collected argarray #1" + + setup_xfail "*-*-*" gdb_test "print argarray\[2\]" \ "\\$\[0-9\]+ = 113$cr" \ "collect $msg: collected argarray #2" + + setup_xfail "*-*-*" gdb_test "print argarray\[3\]" \ "\\$\[0-9\]+ = 114$cr" \ "collect $msg: collected argarray #3" @@ -237,15 +252,30 @@ proc gdb_collect_argarray_test { myargs msg } { run_trace_experiment $msg argarray_test_func # array arg as only argument + + # It isn't clear why is the test assuming the array's elements are + # collected. In C, an array as function parameters is a special + # case; it's just a pointer into the caller's array, and as such, + # that's what normally the debug info describes. Maybe this was + # originaly written for a compiler where array parameters were + # really described as arrays in debug info. + + setup_xfail "*-*-*" gdb_test "print argarray\[0\]" \ "\\$\[0-9\]+ = 111$cr" \ "collect $msg: collected argarray #0" + + setup_xfail "*-*-*" gdb_test "print argarray\[1\]" \ "\\$\[0-9\]+ = 112$cr" \ "collect $msg: collected argarray #1" + + setup_xfail "*-*-*" gdb_test "print argarray\[2\]" \ "\\$\[0-9\]+ = 113$cr" \ "collect $msg: collected argarray #2" + + setup_xfail "*-*-*" gdb_test "print argarray\[3\]" \ "\\$\[0-9\]+ = 114$cr" \ "collect $msg: collected argarray #3" |