From 1d17025506de70cb1d9d5b7a5654e40ce689bf26 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Fri, 12 Jan 2018 18:59:40 +0000 Subject: 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 * gdb.base/continue-after-aborted-step-over.c: New. * gdb.base/continue-after-aborted-step-over.exp: New. --- gdb/testsuite/ChangeLog | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'gdb/testsuite/ChangeLog') diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 7d7c389d98..90ffb4fa44 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2018-01-12 Pedro Alves + + * gdb.base/continue-after-aborted-step-over.c: New. + * gdb.base/continue-after-aborted-step-over.exp: New. + 2018-01-11 Pedro Alves PR remote/22597 -- cgit v1.2.3