public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: pmuldoon@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  tromey/python: 2013-10-14  Phil Muldoon  <pmuldoon@redhat.com>
Date: Mon, 14 Oct 2013 09:15:00 -0000	[thread overview]
Message-ID: <20131014091502.11637.qmail@sourceware.org> (raw)

The branch, tromey/python has been updated
       via  269d883cd0c2fd8a51163e4472963b1b5a9a576e (commit)
      from  aed684a9a6f3dab80262ca21d6c728e99526b37f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 269d883cd0c2fd8a51163e4472963b1b5a9a576e
Author: Phil Muldoon <pmuldoon@redhat.com>
Date:   Mon Oct 14 10:14:20 2013 +0100

    2013-10-14  Phil Muldoon  <pmuldoon@redhat.com>
    
    	* python/python.c (gdbpy_cli): Use current_interp_command_loop and
    	bar invocation from MI.

-----------------------------------------------------------------------

Summary of changes:
 gdb/python/python.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

First 500 lines of diff:
diff --git a/gdb/python/python.c b/gdb/python/python.c
index bfb5599..2c7e89e 100644
--- a/gdb/python/python.c
+++ b/gdb/python/python.c
@@ -1131,9 +1131,12 @@ gdbpy_cli (PyObject *unused1, PyObject *unused2)
 {
   if (! running_python_script || in_cli)
     return PyErr_Format (PyExc_RuntimeError, "cannot invoke CLI recursively");
+  
+  if (ui_out_is_mi_like_p (current_uiout))
+    return PyErr_Format (PyExc_RuntimeError, _("Cannot invoke CLI from MI."));
 
   in_cli = 1;
-  cli_command_loop ();
+  current_interp_command_loop ();
   in_cli = 0;
 
   Py_RETURN_NONE;


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2013-10-14  9:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131014091502.11637.qmail@sourceware.org \
    --to=pmuldoon@sourceware.org \
    --cc=archer-commits@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).