Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [Patch v18 4/4] Add xmethod support to the Python API
Date: Wed, 28 May 2014 20:58:00 -0000	[thread overview]
Message-ID: <CADPb22QTkhbq3F11abh879yKfEsqjT+LvZ35xKYz5sX_8pBNeQ@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gx09MP8RPPr6bu9TfawKASX14d2j3+MkocKU_vtJhN7pA@mail.gmail.com>

On Wed, May 28, 2014 at 1:44 PM, Siva Chandra <sivachandra@google.com> wrote:
> On Tue, May 27, 2014 at 10:02 PM, Doug Evans <xdje42@gmail.com> wrote:
>> Ok, let's do this.
>>
>> extension.c:invoke_xmethod will throw an error if this function
>> returns EXT_LANG_RC_ERROR:
>>
>>   if (rc == EXT_LANG_RC_ERROR)
>>     {
>>       error (_("Error while invoking a xmethod defined in %s"),
>>              worker->extlang->capitalized_name);
>>     }
>
> I did not understand this part. Since you suggest below that
> gdbpy_invoke_xmethod return value * and throw GDB errors for Python
> errors as well, where would invoke_xmethod get RC from?

invoke_method would look like this:

struct value *
invoke_xmethod (struct xmethod_worker *worker, struct value *obj,
                struct value **args, int nargs)
{
  gdb_assert (worker->extlang->ops->invoke_xmethod != NULL);

  return worker->extlang->ops->invoke_xmethod (worker->extlang, worker,
                                               obj, args, nargs);
}

Sorry for the confusion.


  reply	other threads:[~2014-05-28 20:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 21:02 Siva Chandra
2014-05-25 23:31 ` Doug Evans
2014-05-28  5:02   ` Doug Evans
2014-05-28 20:44     ` Siva Chandra
2014-05-28 20:58       ` Doug Evans [this message]
2014-05-28  5:41 ` Doug Evans
2014-05-28 19:12   ` Siva Chandra
2014-05-28 20:31     ` 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=CADPb22QTkhbq3F11abh879yKfEsqjT+LvZ35xKYz5sX_8pBNeQ@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sivachandra@google.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