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: Wed, 20 Nov 2013 00:39:00 -0000	[thread overview]
Message-ID: <CAGyQ6gxHMV6a7kbxu9HCJOgs-kGAGtkvMV6w7fn-SU412sfU3g@mail.gmail.com> (raw)
In-Reply-To: <CADPb22S+g2o7VpxVEPQco8owoxxjECePtYJt=Oh2PNVf4sseEA@mail.gmail.com>

I am working the new patch sets that would address most of your
comments. For one or two, I will probably ask more questions when I
post the patches. But I want to respond to one comment now.

On Tue, Nov 19, 2013 at 3:41 PM, Doug Evans <dje@google.com> wrote:
> For matching on the method, I would just use a string comparison.
> Again, this is for the simple version.  IIUC the API allows for more
> complex mechanisms, but for the start I'd say start small with
> something simple.
> [I can imagine an issue arising with operators, e.g., "operator ()" vs
> "operator()" or some such.  Is handling that with a regexp the best
> way to go?  Dunno.]

For things "operator ()" vs "operator()", I think GDB handles that
before looking up the method. But otherwise, a simple name match can
have problems with template methods as the template argument could be
anything. I am working on setting up tests which illustrate debug
methods for template classes with template methods.


  reply	other threads:[~2013-11-20  0:03 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
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 [this message]
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=CAGyQ6gxHMV6a7kbxu9HCJOgs-kGAGtkvMV6w7fn-SU412sfU3g@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