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/17379] PowerPC: internal-error: value_of_register_lazy: Assertion `frame_id_p (get_frame_id (frame))' failed.
Date: Fri, 12 Sep 2014 12:29:00 -0000	[thread overview]
Message-ID: <bug-17379-4717-KKgKiJyn5P@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17379-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 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  9d9bf2df89db515958b429a1aeb1db38884ba488 (commit)
      from  1cf2f1b045e9e647f6dfd28829ff4592c588dcb7 (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=9d9bf2df89db515958b429a1aeb1db38884ba488

commit 9d9bf2df89db515958b429a1aeb1db38884ba488
Author: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Date:   Fri Sep 12 09:20:25 2014 -0300

    PR tdep/17379: Fix internal-error when stack pointer is invalid.

    The problem is that rs6000_frame_cache attempts to read the stack backchain
via
    read_memory_unsigned_integer, which throws an exception if the stack
pointer is
    invalid.  With this patch, it calls safe_read_memory_integer instead, which
    doesn't throw an exception and allows for safe handling of that situation.

    gdb/ChangeLog
    2014-09-12  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
            Ulrich Weigand� <uweigand@de.ibm.com>

        PR tdep/17379
        * rs6000-tdep.c (rs6000_frame_cache): Use safe_read_memory_integer
        instead of read_memory_unsigned_integer.

    gdb/testcase/ChangeLog
    2014-09-12  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>

        PR tdep/17379
        * gdb.arch/powerpc-stackless.S: New file.
        * gdb.arch/powerpc-stackless.exp: New file.

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

Summary of changes:
 gdb/ChangeLog                                |    7 ++++
 gdb/rs6000-tdep.c                            |   11 +++++--
 gdb/testsuite/ChangeLog                      |    6 ++++
 gdb/testsuite/gdb.arch/powerpc-stackless.S   |   24 +++++++++++++++
 gdb/testsuite/gdb.arch/powerpc-stackless.exp |   42 ++++++++++++++++++++++++++
 5 files changed, 87 insertions(+), 3 deletions(-)
 create mode 100644 gdb/testsuite/gdb.arch/powerpc-stackless.S
 create mode 100644 gdb/testsuite/gdb.arch/powerpc-stackless.exp

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-16462-listarch-gdb-prs=sources.redhat.com@sourceware.org Fri Sep 12 13:00:59 2014
Return-Path: <gdb-prs-return-16462-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 21484 invoked by alias); 12 Sep 2014 13:00:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 21416 invoked by uid 48); 12 Sep 2014 13:00:59 -0000
From: "emachado at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/17379] PowerPC: internal-error: value_of_register_lazy:
 Assertion `frame_id_p (get_frame_id (frame))' failed.
Date: Fri, 12 Sep 2014 13:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: tdep
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emachado at sourceware dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: emachado at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-17379-4717-E9OwFW2KXY@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17379-4717@http.sourceware.org/bugzilla/>
References: <bug-17379-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q3/txt/msg00451.txt.bz2
Content-length: 384

https://sourceware.org/bugzilla/show_bug.cgi?id\x17379

Edjunior Machado <emachado at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

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


  parent reply	other threads:[~2014-09-12 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 20:55 [Bug tdep/17379] New: " emachado at sourceware dot org
2014-09-12  9:17 ` [Bug tdep/17379] " palves at redhat dot com
2014-09-12  9:28 ` uweigand at gcc dot gnu.org
2014-09-12 10:01 ` palves at redhat dot com
2014-09-12 12:29 ` cvs-commit at gcc dot gnu.org [this message]
2014-09-12 13:04 ` emachado at sourceware dot org
2021-09-03 15:05 ` ovilewade9 at gmail dot com

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-17379-4717-KKgKiJyn5P@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).