[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 #2 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  835c559fd59d4ebb3b04d046c1f9f36183db0fe6 (commit)
      from  06eb158633faa8746dd39f19ce784448bb7ece00 (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=835c559fd59d4ebb3b04d046c1f9f36183db0fe6

commit 835c559fd59d4ebb3b04d046c1f9f36183db0fe6
Author: Pedro Alves <palves@redhat.com>
Date:   Tue Jun 3 12:46:46 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 another kfailed
    test.

    gdb/testsuite/
    2014-06-03  Pedro Alves  <palves@redhat.com>

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

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

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

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