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 gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"
Date: Wed, 17 Sep 2014 15:33:00 -0000	[thread overview]
Message-ID: <bug-17384-4717-gvzCNBI9QN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17384-4717@http.sourceware.org/bugzilla/>

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

--- Comment #12 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  5e43d46791c4c66fd83947a12d4f716b561a9103 (commit)
      from  2569ceb0b02cc5569af5f946d89b578510ac5ea1 (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=5e43d46791c4c66fd83947a12d4f716b561a9103

commit 5e43d46791c4c66fd83947a12d4f716b561a9103
Author: Ulrich Weigand <ulrich.weigand@de.ibm.com>
Date:   Wed Sep 17 17:29:27 2014 +0200

    PR gdb/17384: Do not print memory errors in safe_read_memory_integer

    If accessing memory via safe_read_memory_integer fails, that function
    used to print an error message even though callers were perfectly able
    to handle (and even expected!) failures.

    This patch removes the confusing message by changing the routine to
    directly use target_read_memory.

    gdb/ChangeLog:

        PR gdb/17384
        * corefile.c (struct captured_read_memory_integer_arguments): Remove.
        (do_captured_read_memory_integer): Remove.
        (safe_read_memory_integer): Use target_read_memory directly instead
        of catching errors in do_captured_read_memory_integer.

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

Summary of changes:
 gdb/ChangeLog  |    8 ++++++++
 gdb/corefile.c |   50 +++++---------------------------------------------
 2 files changed, 13 insertions(+), 45 deletions(-)

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


  parent reply	other threads:[~2014-09-17 15:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 13:38 [Bug gdb/17384] New: " martin at minimum dot se
2014-09-16  8:48 ` [Bug gdb/17384] " martin at minimum dot se
2014-09-16  9:03 ` palves at redhat dot com
2014-09-16  9:16 ` palves at redhat dot com
2014-09-16 13:41 ` martin at minimum dot se
2014-09-16 13:46 ` martin at minimum dot se
2014-09-16 15:10 ` palves at redhat dot com
2014-09-17  7:57 ` martin at minimum dot se
2014-09-17  9:45 ` martin at minimum dot se
2014-09-17 10:20 ` palves at redhat dot com
2014-09-17 11:23 ` martin at minimum dot se
2014-09-17 11:38 ` palves at redhat dot com
2014-09-17 15:33 ` cvs-commit at gcc dot gnu.org [this message]
2014-09-18  7:15 ` martin at minimum dot se
2014-09-18  7:28 ` palves at redhat dot com
2014-09-18  7:33 ` palves at redhat dot com
2014-09-18  8:44 ` palves at redhat dot com
2014-09-18 17:40 ` palves at redhat dot com
2014-09-19 14:54 ` martin at minimum dot se
2014-09-19 15:25 ` palves at redhat dot com
2014-09-22  9:12 ` martin at minimum dot se
2014-09-22 13:12 ` qiyao at gcc dot gnu.org
2014-09-23  9:23 ` qiyao at gcc dot gnu.org
2014-09-23 12:50 ` martin at minimum dot se
2014-09-24 11:57 ` qiyao at gcc dot gnu.org
2014-10-09  8:10 ` qiyao at gcc dot gnu.org
2014-10-14  8:32 ` martin at minimum dot se
2014-10-14 11:01 ` martin at minimum dot se

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-17384-4717-gvzCNBI9QN@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).