[Bug gdb/17511] Program received signal SIGTRAP, after step to signal handler -> step inside handler -> continue

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

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

--- Comment #3 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  9de00a4aa026297eae42bafd8ab413cfc1a53e3a (commit)
      from  b7a084bebe979a4743540349025561ce82208843 (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=9de00a4aa026297eae42bafd8ab413cfc1a53e3a

commit 9de00a4aa026297eae42bafd8ab413cfc1a53e3a
Author: Pedro Alves <palves@redhat.com>
Date:   Fri Nov 7 15:20:47 2014 +0000

    gdb.base/sigstep.exp: xfail gdb/17511 on i?86 Linux

    Running gdb.base/sigstep.exp with --target=i686-pc-linux-gnu on a
    64-bit kernel naturally trips on PR gdb/17511 as well, given this is a
    kernel bug.

    I haven't really tested a real 32-bit kernel/machine, but given the
    code in question in the kernel is shared between 32-bit and 64-bit,
    I'm quite sure the bug triggers in those cases as well.

    So, simply xfail i?86-*-linux* too.

    gdb/testsuite/
    2014-11-07  Pedro Alves  <palves@redhat.com>

        PR gdb/17511
        * gdb.base/sigstep.exp (in_handler_map) <si+advance>: xfail
        i?86-*-linux*.

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

Summary of changes:
 gdb/testsuite/ChangeLog            |    6 ++++++
 gdb/testsuite/gdb.base/sigstep.exp |    1 +
 2 files changed, 7 insertions(+), 0 deletions(-)

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