Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Abhijit Halder <abhijit.k.halder@gmail.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: PING: [PATCH] Fixing parse errors in c-exp.y
Date: Sat, 24 Sep 2011 10:44:00 -0000	[thread overview]
Message-ID: <CAOhZP9x-QeJMHS_Gtf295=6E30ij6mxR3ZTxGEmAwKRVg0Mm1A@mail.gmail.com> (raw)
In-Reply-To: <CAOhZP9yJmAhfHU_A_UR4xiVkijzbYKUb3tjbdNYnsYTZQHsk+g@mail.gmail.com>

On Sat, Sep 24, 2011 at 2:48 PM, Abhijit Halder
<abhijit.k.halder@gmail.com> wrote:
> Hi all,
>
> This patch is about fixing parse error coming when gdb tries to parse
> a pointer to a function pointer. e.g. (int)(**)(int) and the

This is also a filed bug. (PR 9514).

> associated problem, defined in PR 9837, which says wrong parsing when
> pointers appear in function argument e.g.  (int)(*)(int*)
>
> Please review this.
>
> Thanks,
> Abhijit Halder
>


  reply	other threads:[~2011-09-24 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24 10:37 Abhijit Halder
2011-09-24 10:44 ` Abhijit Halder [this message]
2011-09-25  8:51   ` Abhijit Halder
2011-09-26 19:12 ` Keith Seitz
2011-09-27 10:44   ` Abhijit Halder

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='CAOhZP9x-QeJMHS_Gtf295=6E30ij6mxR3ZTxGEmAwKRVg0Mm1A@mail.gmail.com' \
    --to=abhijit.k.halder@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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