public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/17400] New: buglet in rs6000-tdep.c:skip_prologue Date: Tue, 16 Sep 2014 23:12:00 -0000 [thread overview] Message-ID: <bug-17400-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17400 Bug ID: 17400 Summary: buglet in rs6000-tdep.c:skip_prologue Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: dje at google dot com I happened to be single stepping through this function and noticed the cursor skipping over this particular test. gcc had optimized it out even though I had compiled gdb with -O0. Looking at the test it's easy to see why: it can never succeed. else if ((op & 0xfc1f016a) == 0x7c01016e) // <<<< can never succeed { /* stwux rX,r1,rY */ /* No way to figure out what r1 is going to be. */ fdata->frameless = 0; offset = fdata->offset; continue; } -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-09-16 23:12 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-16 23:12 dje at google dot com [this message] 2024-01-12 15:32 ` [Bug tdep/17400] " ssbssa at sourceware dot 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-17400-4717@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).