public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/16324] New: py-finishbreakpoint.c incorrect frame_id_eq
Date: Fri, 13 Dec 2013 11:25:00 -0000	[thread overview]
Message-ID: <bug-16324-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 16324
           Summary: py-finishbreakpoint.c incorrect frame_id_eq
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: jan.kratochvil at redhat dot com

if (frame_id_eq (frame_id, null_frame_id))
                PyErr_SetString (PyExc_ValueError,
                                 _("Invalid ID for the `frame' object."));

it can never happen as frame_id_eq (null_frame_id, null_frame_id) is false:
     /* Like a NaN, if either ID is invalid, the result is false.
+
  /* Make the sentinel frame's ID valid, but invalid.  That way all
     comparisons with it should fail.  */
  frame->this_id.p = 1;
  frame->this_id.value = null_frame_id;

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


             reply	other threads:[~2013-12-13 11:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 11:25 jan.kratochvil at redhat dot com [this message]
2014-02-24 13:02 ` [Bug python/16324] " pmuldoon at redhat dot com
2022-06-05 16:24 ` tromey at sourceware dot org
2022-10-18 16:33 ` cvs-commit at gcc dot gnu.org
2022-10-18 16:34 ` tromey 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-16324-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: 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).