Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org, dje@google.com
Subject: Re: [patch] [python] Implement stop_p for gdb.Breakpoint
Date: Mon, 07 Mar 2011 22:01:00 -0000	[thread overview]
Message-ID: <m38vwqlkek.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m31v2y4x64.fsf@redhat.com> (Phil Muldoon's message of "Wed, 23	Feb 2011 14:56:19 +0000")

>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:

Phil> +#if HAVE_PYTHON
Phil> +#include "python/python.h"
Phil> +#endif

You can include this header without the #if.
It is designed to work properly even if Python support is not enabled.

Phil> +#if HAVE_PYTHON
Phil> +      /* Evaluate Python breakpoints that have a "condition"
Phil> +	 method implemented.  */
Phil> +      if (b->py_bp_object)
Phil> +	bs->stop = gdbpy_stop_p (b->py_bp_object);
Phil> +#endif

I think you should remove the #if here and have a second implementation
of gdbpy_stop_p that just calls internal_error.  The idea here is that
py_bp_object can only be non-NULL if Python support was actually enabled.

Per the other message, just drop the log-printf stuff from the
submission for now.  We can submit it, or not, later on.  (I think we
should still put it in Fedora though.)

The rest of the code bits look good to me.

Tom


      parent reply	other threads:[~2011-03-07 20:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 16:33 Phil Muldoon
2011-02-23 18:05 ` Eli Zaretskii
2011-02-24  7:02 ` Doug Evans
2011-02-24  9:50   ` Phil Muldoon
     [not found]     ` <AANLkTikXyH+zYkFRoUmihmDYj_nxU5648UnF5T9G-Wte@mail.gmail.com>
2011-02-28 21:19       ` Doug Evans
2011-03-07 16:43         ` Phil Muldoon
2011-03-07 20:52   ` Tom Tromey
2011-03-10  6:47     ` Doug Evans
2011-03-11  1:55       ` Tom Tromey
2011-03-11 11:59         ` Phil Muldoon
2011-03-11 18:27           ` Tom Tromey
2011-03-11 20:59             ` Doug Evans
2011-03-13 22:28               ` Phil Muldoon
2011-03-14 14:49                 ` Tom Tromey
2011-03-14 17:56                   ` Phil Muldoon
2011-03-14 20:01                     ` Tom Tromey
2011-03-14 21:27                     ` Eli Zaretskii
2011-03-11 18:36           ` Tom Tromey
2011-03-07 22:01 ` Tom Tromey [this message]

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=m38vwqlkek.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    /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