Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Debug Methods in GDB Python
Date: Sat, 16 Nov 2013 01:03:00 -0000	[thread overview]
Message-ID: <CAGyQ6gwtj3TEazHJYvVNwbZnN3hh6ZJD_dcG4spZ56hkXaP2ag@mail.gmail.com> (raw)
In-Reply-To: <CADPb22TgkC-KBhAoYvNBueOKrHAFWwvd9TgYaQ2=Oq5qsFoZrA@mail.gmail.com>

On Fri, Nov 15, 2013 at 4:05 PM, Doug Evans <dje@google.com> wrote:
> It would be good to provide enable/disable/info support akin the the
> python pretty-printers.

Yes. I am planning to bring them in the next version of the patches.

> The original pretty-printers used regexps for matching but that was
> IIUC found to be excessively general.
> We might want to avoid them in the basic versions of debug methods.

Do you have an alternate approach in mind?

> I could be wrong but it seemed like errors were handled differently
> than in the pretty-printers.
> The inconsistency doesn't feel warranted.

Yes, there is a difference.

> IIRC the "ext_lang" stuff was going to be deleted, right?

I am not sure. Tom had a comment long time back on this, but his
latest review said that his comments on this might be irrelevant now.
I have renamed some of the pieces related to this in my last patch. Do
you have any specific comments?

> What are debug method groups for?

They are for disabling and enabling a group of debug methods. For
example, they could be used for debugging the debug methods themselves
or writing tests for them: You can disable a group at once instead of
disabling individually.

> One thought I had, and this is mostly for discussion's sake,
> is why stop at providing support for user-defined methods (incl. operators)?
> Why not allow anything that might be "hand called" to be implemented in Python?

I think that could be a fairly straightforward extension. Do you want
it to be done together with this work?

> [One way of implementing user-defined methods/operators was to
> translate, e.g. my_stl_vector[3], into a "pseudo- hand call",
> and then call into Python at the point where we would have hand-called
> the inferior instead.]

IIRC, you had suggested similar ideas earlier as well. However, I have
not gone that route because I thought debug methods/functions should
go through the method/function matching infrastructure. Am I missing
something here?


  reply	other threads:[~2013-11-16  0:54 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
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 [this message]
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=CAGyQ6gwtj3TEazHJYvVNwbZnN3hh6ZJD_dcG4spZ56hkXaP2ag@mail.gmail.com \
    --to=sivachandra@google.com \
    --cc=dje@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