public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Add testcase for GDB hang fixed by previous commit
Date: Fri, 12 Jan 2018 20:00:00 -0000	[thread overview]
Message-ID: <eea61984abfea2c0acdc7e46ec182a14698b3bf9@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT eea61984abfea2c0acdc7e46ec182a14698b3bf9 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: eea61984abfea2c0acdc7e46ec182a14698b3bf9

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.


             reply	other threads:[~2018-01-12 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 20:00 sergiodj+buildbot [this message]
2018-01-12 20:00 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2018-01-12 20:04 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-12 20:19 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-01-12 20:21 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-12 20:26 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-12 20:32 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-12 20:54 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-12 21:29 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-13  4:55 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-13  6:04 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eea61984abfea2c0acdc7e46ec182a14698b3bf9@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).