From: Phil Muldoon <pmuldoon@redhat.com>
To: xdje42@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v1 03/13] script language API for GDB: python.[ch] changes
Date: Fri, 06 Dec 2013 09:43:00 -0000 [thread overview]
Message-ID: <52A19C34.3050206@redhat.com> (raw)
In-Reply-To: <52a1662d.a601430a.7cf1.61b3@mx.google.com>
On 06/12/13 05:52, xdje42@gmail.com wrote:
> This patch contains the changes to python-internal.h, python.c, python.h.
> It defines the "ops" vectors for Python, defines script_language_python
> as the top level interface to Python, and then has a bunch of renamings.
> The functions that implement the script_language_ops "methods" are all
> named ${lang}_${method_name}.
> Functions that were exported to gdb now live in the ops vectors.
Thanks, I am reviewing these today. But, just a quick note.
> @@ -1815,8 +1851,29 @@ finish_python_initialization (void)
> do_cleanups (cleanup);
> }
>
> +/* Return non-zero if Python has successfully initialized.
> + This is the script_languages_ops.initialized "method". */
> +
> +static int
> +gdbpy_initialized (const struct script_language_defn *slang)
> +{
> + return gdb_python_initialized;
> +}
> +
> #endif /* HAVE_PYTHON */
>
> +/* Some code (e.g., MI) wants to know if a particular scripting language
> + successfully initialized.
> + Return non-zero if Python scripting successfully initialized. */
> +
> +int
> +script_lang_python_initialized (void)
> +{
> + if (script_language_python.ops != NULL)
> + return script_language_python.ops->initialized (&script_language_python);
> + return 0;
> +}
> +
This hunk was rejected via patch. All the other patches and hunks in
all the other mails were fine, so weird. Anyway just thought I would
note it, you might need to do a git pull. Or maybe the ^L's got mangled
by the mailer or something.
Cheers,
Phil
next prev parent reply other threads:[~2013-12-06 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 5:52 xdje42
2013-12-06 9:43 ` Phil Muldoon [this message]
2013-12-06 17:19 ` Doug Evans
2013-12-06 12:35 ` Phil Muldoon
2013-12-06 17:22 ` Doug Evans
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=52A19C34.3050206@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.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