public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "uweigand 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 09:28:00 -0000 [thread overview] Message-ID: <bug-17379-4717-TsjKJznP0y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17379-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17379 Ulrich Weigand <uweigand at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uweigand at gcc dot gnu.org --- Comment #2 from Ulrich Weigand <uweigand at gcc dot gnu.org> --- Hi Pedro, the problem was in rs6000_frame_cache, where a read_memory_unsigned_integer would throw an exception if the stack is invalid. This exception was caught somewhere higher up in the frame unwinding logic, but this lead to a situation where frame 0 was marked invalid, which the rest of GDB doesn't really handle well. Edjunior has already posted a patch to the list. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-12 9:28 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 [this message] 2014-09-12 10:01 ` palves at redhat dot com 2014-09-12 12:29 ` cvs-commit at gcc dot gnu.org 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-TsjKJznP0y@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: linkBe 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).