Add testcase for GDB hang fixed by previous commit
authorPedro Alves <palves@redhat.com>
Fri, 12 Jan 2018 18:52:39 +0000 (18:52 +0000)
committerPedro Alves <palves@redhat.com>
Fri, 12 Jan 2018 18:58:04 +0000 (18:58 +0000)
commiteea61984abfea2c0acdc7e46ec182a14698b3bf9
tree2e1d953e638b03ba2f6f673c955fdca27f5e292a
parentbdf2a94aa535016a1640d56e9b2b539c4376bf31
Add testcase for GDB hang fixed by previous commit

This adds a testcase for the previous commit.  The regression was
related to in-line step overs.  The reason we didn't see it on native
x86-64/s390 GNU/Linux testing is that native debugging uses displaced
stepping by default (because native debugging defaults to "maint set
target-non-stop on"), unlike remote debugging.

So in order to trigger the bug with native debugging as well, the
testcase disables displaced stepping explicitly.

Also, instead of using watchpoints to trigger the regression, the
testcase uses a breakpoint at address 0, which should be more
portable.

gdb/testsuite/ChangeLog:
2018-01-12  Pedro Alves  <palves@redhat.com>

* gdb.base/continue-after-aborted-step-over.c: New.
* gdb.base/continue-after-aborted-step-over.exp: New.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/continue-after-aborted-step-over.c [new file with mode: 0644]
gdb/testsuite/gdb.base/continue-after-aborted-step-over.exp [new file with mode: 0644]