From: Doug Evans <dje@google.com>
To: Siva Chandra <sivachandra@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 02:48:00 -0000 [thread overview]
Message-ID: <CADPb22QTmZ9t8MXjpsysWShynj0-HCyFrrFkvh2uEMyJfH3wcw@mail.gmail.com> (raw)
In-Reply-To: <CADPb22S+g2o7VpxVEPQco8owoxxjECePtYJt=Oh2PNVf4sseEA@mail.gmail.com>
On Tue, Nov 19, 2013 at 3:41 PM, Doug Evans <dje@google.com> wrote:
>>> 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?
>
> The name is a tad confusing, though I'm warming up to it.
> The high order bit for me is you're really just abstracting away a
> subset of a much bigger problem space: The abstraction of all calls
> from gdb-proper to the extension language.
For reference sake,
I have a patch that addresses the general problem.
I'll be submitting it after a couple more cleanups are committed.
prev parent reply other threads:[~2013-11-20 2:42 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
2013-11-20 2:48 ` Doug Evans [this message]
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=CADPb22QTmZ9t8MXjpsysWShynj0-HCyFrrFkvh2uEMyJfH3wcw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.com \
--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