diff options
| author | Pedro Alves <palves@redhat.com> | 2018-01-12 18:52:39 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2018-01-12 18:58:04 +0000 |
| commit | eea61984abfea2c0acdc7e46ec182a14698b3bf9 (patch) | |
| tree | 2e1d953e638b03ba2f6f673c955fdca27f5e292a /elfcpp | |
| parent | bdf2a94aa535016a1640d56e9b2b539c4376bf31 (diff) | |
| download | gdb-eea61984abfea2c0acdc7e46ec182a14698b3bf9.zip gdb-eea61984abfea2c0acdc7e46ec182a14698b3bf9.tar.gz gdb-eea61984abfea2c0acdc7e46ec182a14698b3bf9.tar.bz2 | |
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.
Diffstat (limited to 'elfcpp')
0 files changed, 0 insertions, 0 deletions