All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
To: Rakesh Pandit <rakesh.pandit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: option for printing all matching function names
Date: Wed, 5 May 2010 09:44:01 -0300	[thread overview]
Message-ID: <20100505124401.GG970@ghostprotocols.net> (raw)
In-Reply-To: <q2qb401d2531005050445wb33461ecnab0f752909fb4a4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Em Wed, May 05, 2010 at 05:15:20PM +0530, Rakesh Pandit escreveu:
> Hello,
> 
> If we are using pfunct right with option --function, it prints the
> first matched function name. This does not satisfy those cases where
> object file has more then one functions with same name. I would like
> it to print all matching cases not just the first one. Would it be
> acceptable ? Or if it is not acceptable as it may break few scripts
> written by users which are consuming the tool. An alternate
> implementation could be if supplied with an extra option print all
> matches and by default just print first one.
> 
> Suggestions ? If any of above to is acceptable I can straight right
> down a patch accordingly.

well, if you say something like:

pfunct --function do_read --all-units

Meaning that it will print something like:

obj_foo: void do_read(char buffer);
obj_bar: int do_read(char bf, int size);
obj_baz: size_t do_read(int fd, char buf, int ln);

Its useful, send the patch :-)

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe dwarves" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-05-05 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 11:45 option for printing all matching function names Rakesh Pandit
     [not found] ` <q2qb401d2531005050445wb33461ecnab0f752909fb4a4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-05 12:44   ` Arnaldo Carvalho de Melo [this message]
     [not found]     ` <20100505124401.GG970-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2010-05-05 13:12       ` Arnaldo Carvalho de Melo
     [not found]         ` <20100505131230.GA10363-f8uhVLnGfZaxAyOMLChx1axOck334EZe@public.gmane.org>
2010-05-05 14:30           ` Rakesh Pandit

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=20100505124401.GG970@ghostprotocols.net \
    --to=acme-f8uhvlngfzaxayomlchx1axock334eze@public.gmane.org \
    --cc=dwarves-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rakesh.pandit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.