From: Phil Muldoon <pmuldoon@redhat.com>
To: Simone Baratta <conte91@gmail.com>,
Pedro Alves <palves@redhat.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
gdb <gdb@sourceware.org>
Subject: Re: C injection GDB project
Date: Wed, 11 Feb 2015 14:42:00 -0000 [thread overview]
Message-ID: <54DB6A35.30100@redhat.com> (raw)
In-Reply-To: <94F6E835-DD06-4956-BFDF-6B0503CDAE64@gmail.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.
Cheers
Phil
prev parent reply other threads:[~2015-02-11 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877fvopv7x.fsf@gnu.org>
[not found] ` <54DB37D0.1010108@redhat.com>
2015-02-11 12:13 ` Phil Muldoon
2015-02-11 13:53 ` Pedro Alves
[not found] ` <94F6E835-DD06-4956-BFDF-6B0503CDAE64@gmail.com>
2015-02-11 14:42 ` Phil Muldoon [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=54DB6A35.30100@redhat.com \
--to=pmuldoon@redhat.com \
--cc=conte91@gmail.com \
--cc=gdb@sourceware.org \
--cc=jemarch@gnu.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).