From: Eli Zaretskii <eliz@is.elta.co.il>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] GDB interpreters
Date: Mon, 20 May 2002 22:10:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020521080310.4513B-100000@is> (raw)
In-Reply-To: <Pine.GSO.4.33.0205201321010.20482-100000@makita.cygnus.com>
On Mon, 20 May 2002, Keith Seitz wrote:
> Well, here it is. This is the first really big contribution from Apple.
> The two files below implement several functions for setting, getting,
> defining, and querying interpreters.
Thanks!
> I will be adding documentation for the MI part of the GDB manual
Thanks in advance.
However, it sounds, at least for the commands you included in this
patch, like they should be documented in gdb.texinfo, not in the MI part,
since they are not parts of the MI. Or did I miss something?
> interpreter.c (do I need to edit config/djgpp/fnchange.lst?)
I don't think so: you only need to do that if there is another file in
the same directory whose name will clash with interpreter.c after
truncation to 8+3 limits. In this case, I don't see any other files
whose names would clash.
> void
> _initialize_interpreter (void)
> {
> struct cmd_list_element *c;
>
> c = add_set_cmd ("interpreter", class_support,
> var_string,
> &interpreter_p, "Set the interpreter for gdb.", &setlist);
> set_cmd_sfunc (c, set_interpreter_cmd);
> add_show_from_set (c, &showlist);
>
> add_cmd ("interpreters", class_support,
> list_interpreter_cmd,
> "List the interpreters currently available in gdb.", &infolist);
>
> add_cmd ("interpreter-exec", class_support,
> interpreter_exec_cmd,
> "Execute a command in an interpreter. It takes two arguments:\n\
> The first argument is the name of the interpreter to use.\n\
> The second argument is the command to execute.\n", &cmdlist);
> }
Can we have completion on known interpreter names in these commands? The
default completer function completes on symbols from the inferior, which
is really not a good idea in this case ;-)
next prev parent reply other threads:[~2002-05-21 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 13:46 Keith Seitz
2002-05-20 22:10 ` Eli Zaretskii [this message]
2002-05-21 9:14 ` Keith Seitz
2002-05-21 9:23 ` Keith Seitz
2002-05-21 13:27 ` Keith Seitz
2002-05-21 18:41 ` Eli Zaretskii
2002-05-24 15:00 ` Andrew Cagney
2002-05-24 15:38 ` Andrew Cagney
2002-05-24 16:20 ` Keith Seitz
2002-05-28 17:26 ` Keith Seitz
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=Pine.SUN.3.91.1020521080310.4513B-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=keiths@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