Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Bob Rossi <bob_rossi@cox.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Adding -file-list-exec-source-file command to GDB/MI
Date: Wed, 02 Apr 2003 21:59:00 -0000	[thread overview]
Message-ID: <3E8B5D5B.5000700@redhat.com> (raw)
In-Reply-To: <20030402194626.GD13251@white>

> This change essentially adds the command -file-list-exec-source-file to
> the mi commands.
> 
> * mi-cmd-file.c:    Added file to implement mi file commands.
> * mi-getopt.c:      Added mi_valid_noargs to verify if a set of
>                     parameters passed to an MI function has no arguments
> * mi-getopt.h:      Prototyped mi_valid_noargs
> * mi-cmds.c:        Added -file-list-exec-source-file command.
> * mi-cmds.h:        Added -file-list-exec-source-file to proto list.
> * doc/gdb.texinfo:  Document -file-list-exec-source-file.
> * mi-file.exp:      Added testcase to test -file-list-exec-source-file.

Yes, ok.  Just tweak the below GNU coding probs before committing.


> +int 
> +mi_valid_noargs(const char *prefix, int argc, char **argv)

	mi_valid_noargs (

> +{
> +  int optind = 0;
> +  char *optarg;
> +  static struct mi_opt opts[] =
> +  {
> +    0
> +  };
> +
> +  if ( mi_getopt(prefix, argc, argv, opts, &optind, &optarg) == -1 )

	if (mi_getopt (prefix, ...., &optarg) == -1)

> +    return 1;
> +  else
> +    return 0;
> +}

Andrew




  reply	other threads:[~2003-04-02 21:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 20:24 Bob Rossi
2003-04-02 21:59 ` Andrew Cagney [this message]
2003-04-03  2:54 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2003-04-02 20:24 Bob Rossi
2003-03-29  0:41 Bob Rossi
2003-03-31  5:38 ` Andrew Cagney
2003-03-31 18:46   ` Bob Rossi
2003-03-31 18:56     ` Andrew Cagney
2003-04-02 16:15   ` Bob Rossi
2003-04-02 16:27     ` Andrew Cagney
2003-03-20 22:44 Bob Rossi
2003-03-21  4:34 ` Eli Zaretskii
2003-03-21  9:53 ` Jason Molenda
2003-03-21 13:16   ` Bob Rossi
2003-03-28 15:26     ` Andrew Cagney
2003-03-30  4:06       ` Bob Rossi
2003-03-31  4:22         ` Andrew Cagney
2003-03-31  8:13           ` Jason Molenda
2003-03-31 14:31             ` Andrew Cagney
2003-03-31 17:16               ` Jason Molenda
2003-03-31 18:52                 ` Andrew Cagney
2003-03-31 19:20                   ` Jason Molenda
2003-03-31 20:12                     ` Andrew Cagney
2003-03-26 22:48 ` Andrew Cagney
2003-03-28 14:35   ` Bob Rossi
2003-03-28 15:30 ` Andrew Cagney
2003-03-28 16:05   ` Bob Rossi
2003-03-28 16:10     ` Daniel Jacobowitz
2003-03-10  0:31 Bob Rossi
2003-03-10  4:28 ` Eli Zaretskii
2003-03-18  2:10   ` Bob Rossi
2003-03-18  5:46     ` Eli Zaretskii
2003-02-10 22:28 Michael Elizabeth Chastain
2003-02-10 22:15 Bob Rossi
2003-02-11  6:39 ` Eli Zaretskii
2003-02-13  3:00   ` Bob Rossi

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=3E8B5D5B.5000700@redhat.com \
    --to=ac131313@redhat.com \
    --cc=bob_rossi@cox.net \
    --cc=gdb-patches@sources.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