Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: [URGENT] Ideas for Google Summer of Code
Date: Fri, 21 Feb 2014 10:57:00 -0000	[thread overview]
Message-ID: <5307239F.1000509@redhat.com> (raw)
In-Reply-To: <m3ha7uvrvm.fsf@redhat.com>

On 02/19/2014 07:12 PM, Sergio Durigan Junior wrote:

> I am going to propose some ideas for GSoC on behalf of GDB today.  The
> deadline ends 10 hours from now (i.e., 6h UTC approx.), so it is pretty
> tight.  Here is a brief list of things that I am planning:
> 
> - gdbmicli project, from Jan Kratochvil.  Jan will send me a short
>   e-mail with the details about this project.
> 
> - ARI revamp.  This is a personal itch.  I'd like to improve ARI so that
>   it is more useful to us.  I will about some paragraph to describe this
>   task.
> 
> I thought about other tasks (support for pipes on "run", setting up
> buildbots, etc.), but dropped those ideas.  If anyone else want to
> propose something, please let us/me know.

I'm too late now, one thought just crossed my mind: it's kind of
odd that GDB has all this pretty printing machinery in place, but doesn't
have pretty printers for its own structures, like struct type/main_type,
and VECs.  :-P  It'd be nice to address that.  :-)

-- 
Pedro Alves


  parent reply	other threads:[~2014-02-21 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 19:12 Sergio Durigan Junior
2014-02-20  7:31 ` Joel Brobecker
2014-02-20 13:48   ` Sergio Durigan Junior
2014-02-21  9:55   ` Pedro Alves
2014-02-21 18:53     ` Sergio Durigan Junior
2014-02-21 10:57 ` Pedro Alves [this message]
2014-02-21 18:24   ` Tom Tromey
2014-02-21 19:00     ` Jan Kratochvil
2014-02-21 18:54   ` Sergio Durigan Junior

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=5307239F.1000509@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=sergiodj@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