Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Abhijit Halder <abhijit.k.halder@gmail.com>,
	"gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: GDB plugin
Date: Tue, 08 May 2012 15:05:00 -0000	[thread overview]
Message-ID: <20120508150510.GZ15555@adacore.com> (raw)
In-Reply-To: <871umuwzve.fsf@fleche.redhat.com>

> I think most users are better off writing extensions in Python.
> We can expose more internals to Python as needed for this.

I very much agree.

-- 
Joel


  reply	other threads:[~2012-05-08 15:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 16:21 Abhijit Halder
2012-05-07 20:18 ` Tom Tromey
2012-05-08  5:46   ` Abhijit Halder
2012-05-08 14:20     ` Tom Tromey
2012-05-08 15:05       ` Joel Brobecker [this message]
2012-05-08 15:21         ` Mark Kettenis
2012-05-08 22:06     ` André Pönitz
2012-05-09  4:28       ` Abhijit Halder
2012-05-08  6:38   ` Hui Zhu
2012-05-08 13:46     ` Tom Tromey
2012-05-08 14:38     ` Matt Rice
2012-05-08 14:47       ` Paul_Koning
2012-05-08 14:58         ` Matt Rice

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=20120508150510.GZ15555@adacore.com \
    --to=brobecker@adacore.com \
    --cc=abhijit.k.halder@gmail.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