[URGENT] Ideas for Google Summer of Code

[URGENT] Ideas for Google Summer of Code

[Sergio Durigan Junior]

Hi,

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.

Thanks,

-- 
Sergio

Re: [URGENT] Ideas for Google Summer of Code

[Joel Brobecker]

Thanks for doing that, Sergio!

> - 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.

What would be really useful is if we could run it as a commit hook
locally :).

-- 
Joel

Re: [URGENT] Ideas for Google Summer of Code

[Sergio Durigan Junior]

On Thursday, February 20 2014, Joel Brobecker wrote:

> Thanks for doing that, Sergio!
>
>> - 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.
>
> What would be really useful is if we could run it as a commit hook
> locally :).

Thanks Joel!  I will make sure I remember this when we start working on
the task :-).

-- 
Sergio

Re: [URGENT] Ideas for Google Summer of Code

[Pedro Alves]

On 02/20/2014 07:31 AM, Joel Brobecker wrote:
> Thanks for doing that, Sergio!
> 
>> - 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.
> 
> What would be really useful is if we could run it as a commit hook
> locally :).

Or even before commit -- it would be nice if it were super easy
to run the ari at any time.  Something like "make check-ari".

On the subject, the Linux kernel has this checkpatch.pl script
that automates checking a patch for common issues.  Porting that
(or rewrite something along those lines) for GNU/GDB would be
super neat, I think.

 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/scripts/checkpatch.pl
 http://omappedia.org/wiki/Releasing_to_Linux_kernel_using_patches_and_emails#Checking_tools

-- 
Pedro Alves

Re: [URGENT] Ideas for Google Summer of Code

[Pedro Alves]

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

Re: [URGENT] Ideas for Google Summer of Code

[Tom Tromey]

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

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

There's a bit in the delightfully-named gdb/gdb-gdb.py.
At least for me it doesn't trigger by default though.

Tom

Re: [URGENT] Ideas for Google Summer of Code

[Sergio Durigan Junior]

On Friday, February 21 2014, Pedro Alves wrote:

> Or even before commit -- it would be nice if it were super easy
> to run the ari at any time.  Something like "make check-ari".

The original idea described in the wiki is to integrate the ARI into
"make check", or create a "make check-ari", as you said.

> On the subject, the Linux kernel has this checkpatch.pl script
> that automates checking a patch for common issues.  Porting that
> (or rewrite something along those lines) for GNU/GDB would be
> super neat, I think.

Yeah, that is the first thing I thought, too.  It would also be good to
have something in the lines of get_maintainers.pl, and create the habit
to Cc the non-global maintainers when submitting patches to some area,
for example.

Thanks,

-- 
Sergio

Re: [URGENT] Ideas for Google Summer of Code

[Sergio Durigan Junior]

On Friday, February 21 2014, Pedro Alves wrote:

> 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.  :-)

You're not late!  We're allowed to edit/extend the page after the
deadline, there's no problem :-).  I will add this idea as well, thanks!

-- 
Sergio

Re: [URGENT] Ideas for Google Summer of Code

[Jan Kratochvil]

On Fri, 21 Feb 2014 19:24:48 +0100, Tom Tromey wrote:
> There's a bit in the delightfully-named gdb/gdb-gdb.py.
> At least for me it doesn't trigger by default though.

Do you have 'set auto-load safe-path' set?

gdb -iex "set auto-load safe-path $PWD/gdb-gdb.py" -ex 'set pagination off' -ex 'b value_type' -ex r -ex finish -ex 'p *$->main_type' --args ./gdb -ex 'ptype struct main_type' ./gdb
[...]
$2 = 
{name = 0x600400086a30 "int",
 tag_name = 0x0,
 code = TYPE_CODE_INT,
 flags = [],
 owner = 0x6062000e2310 (gdbarch),
 target_type = 0x0,
 vptr_basetype = 0x0,
 type_specific_field = TYPE_SPECIFIC_NONE}

Without gdb-gdb.py it would be:
$2 = {code = TYPE_CODE_INT, flag_unsigned = 0, flag_nosign = 0, flag_stub = 0, flag_target_stub = 0, flag_static = 0, flag_prototyped = 0, flag_incomplete = 0, flag_varargs = 0, flag_vector = 0, flag_stub_supported = 0, flag_gnu_ifunc = 0, flag_fixed_instance = 0, flag_objfile_owned = 0, flag_declared_class = 0, flag_flag_enum = 0, type_specific_field = TYPE_SPECIFIC_NONE, nfields = 0, vptr_fieldno = -1, name = 0x600400086a30 "int", tag_name = 0x0, owner = {objfile = 0x6062000e2310, gdbarch = 0x6062000e2310}, target_type = 0x0, flds_bnds = {fields = 0x0, bounds = 0x0}, vptr_basetype = 0x0, type_specific = {cplus_stuff = 0x0, gnat_stuff = 0x0, floatformat = 0x0, func_stuff = 0x0}}


Jan