Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Abderrahim KITOUNI <a.kitouni@gmail.com>
To: tromey@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re : New language support : Vala
Date: Fri, 06 Mar 2009 18:44:00 -0000	[thread overview]
Message-ID: <3d6b0edb0903061044m2aa8671cn55940f43bc7db9a9@mail.gmail.com> (raw)
In-Reply-To: <m3fxi3ll1s.fsf@fleche.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

2009/2/24, Tom Tromey <tromey@redhat.com>:
> It is worth mentioning where you built and tested this.  Also, you may
> want to consider test suite additions for the vala support...
I built this on a (Debian) GNU/Linux x86, if someone finds a problem
on another platform, I'll be happy to fix it. I'll try to send another
patch with tests later.
>
> I don't know whether your FSF paperwork has gone through.  I don't
> have a way to look that up any more; maybe someone else could find
> out.
Yes, I received the letter.
[...]
> vala-lang.c, vala-lang.h, and vala-print.c all need copyright headers.
> You can copy one from just about any other .c file in gdb; just make
> sure to update the first line (which describes the purpose of the
> file) and the years.
I just forgot to add this (and print_typedef)
[...]
> I am not sure if you want to be using safe-ctype.h or ctype.h.
I don't know myself, I just need toupper (and isupper in the linespec patch).
[...]
> +  target_read_string (value_as_address (name), &type_name, 100, NULL);
>
> That '100' looks odd.  It would probably be better to use the new
> string-reading code that Thiago put in; see valprint.c:read_string.
I didn't find a better solution (read_string returns a gdb_byte* and I don't
know how to convert it).
>
> Also, I think the code should properly handle errors.
In vala_real_type ? Yes, but I didn't find a way to do it, testing for null
pointers isn't sufficient.

Here is a new version of the patch, I think I fixed everything (except the
read_string above), and another patch to deal with linespec parsing for Vala
(this one is relatively small).

Abderrahim

[-- Attachment #2: gdb-vala-rev2.patch.gz --]
[-- Type: application/x-gzip, Size: 7318 bytes --]

[-- Attachment #3: gdb-vala-linespec.patch.gz --]
[-- Type: application/x-gzip, Size: 1819 bytes --]

  reply	other threads:[~2009-03-06 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07 14:07 Abderrahim KITOUNI
2009-02-07 19:43 ` Tom Tromey
2009-02-09 13:05   ` Abderrahim KITOUNI
2009-02-19  8:29     ` Re : " Abderrahim KITOUNI
2009-02-24 19:58       ` Tom Tromey
2009-03-06 18:44         ` Abderrahim KITOUNI [this message]
2009-04-14  0:29           ` Tom Tromey
2009-04-14  7:21             ` Eli Zaretskii

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=3d6b0edb0903061044m2aa8671cn55940f43bc7db9a9@mail.gmail.com \
    --to=a.kitouni@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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