public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/18605] single step over ARM Cortex 'udiv' instruction
Date: Tue, 30 Jun 2015 08:26:00 -0000	[thread overview]
Message-ID: <bug-18605-4717-MIf07wd379@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18605-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Yao Qi <qiyao@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7b9be803fed8f500b512d5685773c84fffcdf63f

commit 7b9be803fed8f500b512d5685773c84fffcdf63f
Author: Yao Qi <yao.qi@linaro.org>
Date:   Tue Jun 30 09:24:43 2015 +0100

    Handle media instructions in arm software single step.

    This patch fixes PR 18605 which is about incorrectly decoding media
    instructions in software single step.

    gdb:

    2015-06-30  Yao Qi  <yao.qi@linaro.org>

        PR tdep/18605
        * arm-tdep.c (arm_get_next_pc_raw): Break for media
        instructions.

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


  parent reply	other threads:[~2015-06-30  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  8:58 [Bug gdb/18605] New: " m.krivtsov at samsung dot com
2015-06-26  9:00 ` [Bug gdb/18605] " m.krivtsov at samsung dot com
2015-06-26  9:00 ` m.krivtsov at samsung dot com
2015-06-26 10:57 ` m.krivtsov at samsung dot com
2015-06-26 14:52 ` qiyao at gcc dot gnu.org
2015-06-29 16:33 ` [Bug tdep/18605] " qiyao at gcc dot gnu.org
2015-06-30  8:26 ` cvs-commit at gcc dot gnu.org [this message]
2015-06-30  8:47 ` qiyao at gcc dot gnu.org

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=bug-18605-4717-MIf07wd379@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).