Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: GSoC
Date: Tue, 07 Feb 2017 22:11:00 -0000	[thread overview]
Message-ID: <dbd9d4c4970c1474a2a17f18798a5240@polymtl.ca> (raw)
In-Reply-To: <b04f68f9-6fb2-3e0f-6eca-c68e64eb4f83@redhat.com>

On 2017-02-07 16:40, Phil Muldoon wrote:
> From an idea standpoint I'd love to see the underpinnings of inferior
> control* capabilities from scripting languages. Perhaps a class that
> registered scripting languages can call (currently Python and Guile)
> to affect control of an inferior, with feedback, from an interface. It
> would ideally abstract all the horrible details from the scripting
> language.
> 
> Note, I do not think this will be an easy project, but it will
> introduce the person to the community as, I think, they will have to
> question it quite closely to implement the semantics and exceptions
> involved in inferior control to an external interface.
> 
> Cheers,
> 
> Phil
> 
> * Inferior control being more than being a gdb.command call and hoping
>   things go ok.

I think that's a great idea, it's something that a lot of people ask 
for.  I think it's a good thing to have project ideas that range from 
easy to difficult, as long as it's clearly documented so that the 
potential candidates make informed choices.

Simon


  reply	other threads:[~2017-02-07 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 21:00 GSoC Simon Marchi
2017-02-07 21:40 ` GSoC Phil Muldoon
2017-02-07 22:11   ` Simon Marchi [this message]
2017-02-07 21:41 ` GSoC Jose E. Marchesi
2017-02-07 22:13   ` GSoC Simon Marchi
2017-02-08 17:12 ` GSoC Tom Tromey
2017-02-09 15:48   ` GSoC Simon Marchi
2017-02-09 18:59     ` GSoC Tom Tromey
2017-02-09 21:35     ` GSoC Simon Marchi

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=dbd9d4c4970c1474a2a17f18798a5240@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb@sourceware.org \
    --cc=pmuldoon@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