espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-06-26 13:56:22 +08:00
Code Issues Packages Projects Releases Wiki Activity

* gdb.trace/collection.exp (gdb_collect_args_test)

Browse Source 
(gdb_collect_argarray_test): XFAIL the tests that assume the
	argarray argument's elements are collected.
This commit is contained in:
Pedro Alves
2010-04-01 00:55:03 +00:00
parent dde5d5bf85
commit 0db9b91c94
2 changed files with 36 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
2010-04-01 Pedro Alves <pedro@codesourcery.com>
* gdb.trace/collection.exp (gdb_collect_args_test)
(gdb_collect_argarray_test): XFAIL the tests that assume the
argarray argument's elements are collected.
2010-03-31 Jan Kratochvil <jan.kratochvil@redhat.com> 2010-03-31 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.dwarf2/dw2-bad-parameter-type.exp, * gdb.dwarf2/dw2-bad-parameter-type.exp,

30
gdb/testsuite/gdb.trace/collection.exp
View File

@ -166,15 +166,30 @@ proc gdb_collect_args_test { myargs msg } {
"collect $msg: collected arg struct member double" "collect $msg: collected arg struct member double"
# array arg as one of several args (near end of list) # 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\]" \ gdb_test "print argarray\[0\]" \
"\\$\[0-9\]+ = 111$cr" \ "\\$\[0-9\]+ = 111$cr" \
"collect $msg: collected argarray #0" "collect $msg: collected argarray #0"
setup_xfail "*-*-*"
gdb_test "print argarray\[1\]" \ gdb_test "print argarray\[1\]" \
"\\$\[0-9\]+ = 112$cr" \ "\\$\[0-9\]+ = 112$cr" \
"collect $msg: collected argarray #1" "collect $msg: collected argarray #1"
setup_xfail "*-*-*"
gdb_test "print argarray\[2\]" \ gdb_test "print argarray\[2\]" \
"\\$\[0-9\]+ = 113$cr" \ "\\$\[0-9\]+ = 113$cr" \
"collect $msg: collected argarray #2" "collect $msg: collected argarray #2"
setup_xfail "*-*-*"
gdb_test "print argarray\[3\]" \ gdb_test "print argarray\[3\]" \
"\\$\[0-9\]+ = 114$cr" \ "\\$\[0-9\]+ = 114$cr" \
"collect $msg: collected argarray #3" "collect $msg: collected argarray #3"
@ -237,15 +252,30 @@ proc gdb_collect_argarray_test { myargs msg } {
run_trace_experiment $msg argarray_test_func run_trace_experiment $msg argarray_test_func
# array arg as only argument # 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\]" \ gdb_test "print argarray\[0\]" \
"\\$\[0-9\]+ = 111$cr" \ "\\$\[0-9\]+ = 111$cr" \
"collect $msg: collected argarray #0" "collect $msg: collected argarray #0"
setup_xfail "*-*-*"
gdb_test "print argarray\[1\]" \ gdb_test "print argarray\[1\]" \
"\\$\[0-9\]+ = 112$cr" \ "\\$\[0-9\]+ = 112$cr" \
"collect $msg: collected argarray #1" "collect $msg: collected argarray #1"
setup_xfail "*-*-*"
gdb_test "print argarray\[2\]" \ gdb_test "print argarray\[2\]" \
"\\$\[0-9\]+ = 113$cr" \ "\\$\[0-9\]+ = 113$cr" \
"collect $msg: collected argarray #2" "collect $msg: collected argarray #2"
setup_xfail "*-*-*"
gdb_test "print argarray\[3\]" \ gdb_test "print argarray\[3\]" \
"\\$\[0-9\]+ = 114$cr" \ "\\$\[0-9\]+ = 114$cr" \
"collect $msg: collected argarray #3" "collect $msg: collected argarray #3"