From: Phil Muldoon <pmuldoon@redhat.com>
To: simon.marchi@polymtl.ca
Cc: gdb@sourceware.org
Subject: Re: GSoC
Date: Tue, 07 Feb 2017 21:40:00 -0000 [thread overview]
Message-ID: <b04f68f9-6fb2-3e0f-6eca-c68e64eb4f83@redhat.com> (raw)
In-Reply-To: <edb7fcc880be7c063b31451376903581@polymtl.ca>
On 07/02/17 21:00, Simon Marchi wrote:
> Hi everybody,
>
> A friend of mine suggested that the GDB project should participate in the Google Summer of Code. However, the deadline to register as a mentoring organization is this Thursday, in two days! So we need to act fast if we want to participate. From what I can see, the application process is relatively straightforward, but somebody needs to take care of it (I don't think it has to be the person who will be the mentor, since this may depend on the actual chosen project). I can be that somebody if nobody else wants to.
>
> First of all, I have seen that GDB has been accepted as a mentoring organization in the past:
>
> - https://sourceware.org/gdb/wiki/SummerOfCode2014/Ideas
> - https://sourceware.org/gdb/wiki/SummerOfCode2011/Ideas
> - https://sourceware.org/gdb/wiki/SummerOfCode2009/Proposal
> - https://sourceware.org/gdb/wiki/SummerOfCode2009/Ideas
>
> It would be interesting to gather some feedback from those who lead this initiative in the past. Would you suggest trying to go for it again? Why, why not?
>
> About the actual projects ideas, I'm sure we will be able to collect good ideas from the members of the community. There's always the ProjectIdeas page on the wiki [1] to get some inspiration. On my side, there's the output colouring support which I'd like to see become a reality some day :).
>
> Simon
>
> [1] https://sourceware.org/gdb/wiki/ProjectIdeas
>
>
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.
next prev parent reply other threads:[~2017-02-07 21:40 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 ` Phil Muldoon [this message]
2017-02-07 22:11 ` GSoC Simon Marchi
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=b04f68f9-6fb2-3e0f-6eca-c68e64eb4f83@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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