OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix FAIL: gdb.ada/small_reg_param.exp: continue to call_me

Browse Source 
If enough information is provided by the compiler, the debugger
now prints the entry value of various parameters:

    (gdb) continue
    Continuing.

    Breakpoint 2, pck.call_me (w=w@entry=50) at [...]
    20            Last_Word := W;

This patch adjusts the expected output to allow an optional
"w@entry=" in the parameter value.

gdb/testsuite/ChangeLog:

        * gdb.ada/small_reg_param.exp: Accept optional entry value
        for parameter "w".
This commit is contained in:
Joel Brobecker 2013-07-10 00:10:37 +00:00
parent 52cd8b7d70
commit 7d7c647756
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2013-07-09 Joel Brobecker <brobecker@adacore.com>
* gdb.ada/small_reg_param.exp: Accept optional entry value
for parameter "w".
2013-07-09 Joel Brobecker <brobecker@adacore.com>
* gdb.ada/small_reg_param.exp: Remove trailing space.

2
gdb/testsuite/gdb.ada/small_reg_param.exp
View File

@ -33,7 +33,7 @@ gdb_breakpoint "call_me"
# Continue until we hit the breakpoint inside `Call_Me'. We verify
# that the parameter value is correct.
gdb_test "continue" \
"Breakpoint .*, pck\\.call_me \\(w=50\\) at .*/pck.adb:.*" \
"Breakpoint .*, pck\\.call_me \\(w=(w@entry=)?50\\) at .*/pck.adb:.*" \
"continue to call_me"
# And just to make sure, we also verify that the parameter value