Expect optional "arch=" when executing "-stack-list-frames" on gdb.arch/amd64-invalid...
authorSergio Durigan Junior <sergiodj@redhat.com>
Tue, 18 Sep 2018 17:53:43 +0000 (13:53 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Tue, 18 Sep 2018 17:54:02 +0000 (13:54 -0400)
commit5031d0ae0b9fb1a42eb8ff9d2b5098a56774cee1
tree7bed3bfe2c8a65edcdb376141ddb0c063b7a20e1
parentb4c0d1a440d054cd198041ddf0ba43b83794186f
Expect optional "arch=" when executing "-stack-list-frames" on gdb.arch/amd64-invalid-stack-top.exp

Another case of incomplete regexp.  The problem is very similar to the
one happening with gdb.arch/amd64-invalid-stack-middle.exp.

The output when GDB is compiled with "--enable-targets" is:

  (gdb) interpreter-exec mi "-stack-list-frames"
  ^done,stack=[frame={level="0",addr="0x00000000004005e7",func="func2",arch="i386:x86-64"}]

While the output when "--enable-targets" is not specified is:

  (gdb) interpreter-exec mi "-stack-list-frames"
  ^done,stack=[frame={level="0",addr="0x00000000004005e7",func="func2"}]

The fix is, again, to extend the current regexp and expect for the
optional "arch=" part.  With this patch, the test now passes on both
scenarios.

OK?

gdb/testsuite/ChangeLog:
2018-09-18  Sergio Durigan Junior  <sergiodj@redhat.com>

* gdb.arch/amd64-invalid-stack-top.exp: Expect optional
"arch=" keyword when executing "-stack-list-frames".
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp