Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Debug Methods in GDB Python
Date: Fri, 10 May 2013 19:55:00 -0000	[thread overview]
Message-ID: <CAGyQ6gw_-MOu4Y9D+mUf-A55_Ms+j9JAmM9dU0y8PdJw73EkNw@mail.gmail.com> (raw)
In-Reply-To: <87r4hefx59.fsf@fleche.redhat.com>

On Fri, May 10, 2013 at 12:33 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:
>
> Siva> Attached is a new version of the patch which I have now regression
> Siva> tested. Except for tests and docs, I think it is complete wrt the
> Siva> feature set I have in mind. Hence, the caveats from the previous mail
> Siva> still apply.
>
> I'm sorry about the delay here.

Thanks a lot for taking a look. I have had to be away from this work
myself and I will continue to be away for at least a week more. Hence,
I will respond to your comments in detail late May/early June.

For my own reference, I am summarizing your comments as follows:

1. The ext_fn_object should use the GDB style "virtual method" approach.
2. Python related exceptions and error checking are missing.
3. More functions could be static and function comments are missing.
4. Copy-paste errors.
5. One specific comment about thread safety and GIL.

It would also be good to get feedback on the Python side API that I
put together.

Thanks,
Siva Chandra


  reply	other threads:[~2013-05-10 19:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 21:22 Siva Chandra
2013-01-29  1:51 ` Siva Chandra
2013-02-25 23:02   ` Siva Chandra
2013-05-10 19:33   ` Tom Tromey
2013-05-10 19:55     ` Siva Chandra [this message]
2013-05-14 19:33       ` Tom Tromey
2013-06-17 19:10         ` Siva Chandra
2013-07-22 20:47           ` Tom Tromey
2013-11-12  2:56             ` Siva Chandra
2013-11-15 22:28               ` Tom Tromey
2013-11-16  0:05                 ` Siva Chandra
2013-11-16  0:54                   ` Doug Evans
2013-11-16  1:03                     ` Siva Chandra
2013-11-16  2:48                       ` Siva Chandra
2013-11-20  0:03                         ` Doug Evans
2013-11-19 23:52                       ` Doug Evans
2013-11-20  0:39                         ` Siva Chandra
2013-11-20  2:48                         ` 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=CAGyQ6gw_-MOu4Y9D+mUf-A55_Ms+j9JAmM9dU0y8PdJw73EkNw@mail.gmail.com \
    --to=sivachandra@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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