This is the mail archive of the
mailing list for the GDB project.
Re: C injection GDB project
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Simone Baratta <conte91 at gmail dot com>, Pedro Alves <palves at redhat dot com>, "Jose E. Marchesi" <jemarch at gnu dot org>, gdb <gdb at sourceware dot org>
- Date: Wed, 11 Feb 2015 14:41:57 +0000
- Subject: Re: C injection GDB project
- Authentication-results: sourceware.org; auth=none
- References: <877fvopv7x dot fsf at gnu dot org> <54DB37D0 dot 1010108 at redhat dot com> <54DB4767 dot 4060006 at redhat dot com> <94F6E835-DD06-4956-BFDF-6B0503CDAE64 at gmail dot com>
On 11/02/15 13:23, Simone Baratta wrote:
> Good morning to all;
> Maybe this could be a project for the 2015 gsoc? Projects applications have begun in these days.
> I would be interested too in participating in the code injection project; I have quite a strong confidence with C, C++ and gdb, although not with the advanced features of the latter.
> Also, I will have to start my master thesis project in the next months, could this be interesting for you? It would give me the possibility to work on it full time for some months.
> Thanks in advance,
I have no objection. All help is appreciated. But...
I thought that GSoC project had to refer to a concrete and coherent
functional part of a project. Or a feature. I would really advise
against doing things like the C++ GCC plug-in as a GSoC project that
has an expectation of being finished at the end. It is a fierce
complex part of the project.
That being said if it can be sub-divided into some part that is
acceptable to those moderators of the project, I say sure, go ahead.