[Bug breakpoints/17000] user breakpoint not inserted if software-single-step at same location

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17000

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  9ba6657a6b81a02dca9071ec14cbcef970f0ca07 (commit)
      from  522c09bf63a4b235e6fde07a5e389f2a533cfe0f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ba6657a6b81a02dca9071ec14cbcef970f0ca07

commit 9ba6657a6b81a02dca9071ec14cbcef970f0ca07
Author: Pedro Alves <palves@redhat.com>
Date:   Fri May 30 17:21:02 2014 +0100

    PR breakpoints/17000: user breakpoint not inserted if software-single-step
at same location - test

    GDB gets confused when removing a software single-step breakpoint that
    is at the same address as another breakpoint.  Add a kfailed test.

    gdb/testsuite/
    2014-05-30  Pedro Alves  <palves@redhat.com>

        PR breakpoints/17000
        * gdb.base/sss-bp-on-user-bp.c: New file.
        * gdb.base/sss-bp-on-user-bp.exp: New file.

-----------------------------------------------------------------------

Summary of changes:
 gdb/testsuite/ChangeLog                      |    6 +++
 gdb/testsuite/gdb.base/sss-bp-on-user-bp.c   |   30 +++++++++++++++
 gdb/testsuite/gdb.base/sss-bp-on-user-bp.exp |   52 ++++++++++++++++++++++++++
 3 files changed, 88 insertions(+), 0 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/sss-bp-on-user-bp.c
 create mode 100644 gdb/testsuite/gdb.base/sss-bp-on-user-bp.exp

-- 
You are receiving this mail because:
You are on the CC list for the bug.