From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Give every interpreter a command_loop_proc.
Date: Thu, 05 Sep 2013 17:13:00 -0000 [thread overview]
Message-ID: <5228BBB9.4020904@redhat.com> (raw)
In-Reply-To: <5228B883.2010602@broadcom.com>
On 09/05/2013 05:59 PM, Andrew Burgess wrote:
> 2013-09-05 Andrew Burgess <aburgess@broadcom.com>
>
> * gdb/cli/cli-interp.c (_initialize_cli_interp): Add a
> command_loop_proc to interp_procs.
> * gdb/event-top.c (cli_command_loop): Change signature to match
> interp_command_loop_ftype.
> * gdb/event-top.h (cli_command_loop): Same.
> * gdb/interps.c (interp_new): Require every interpreter to have a
> command_loop_proc.
> (current_interp_command_loop): Just call the command_loop_proc on
> the current interpreter.
> * gdb/tui/tui-interp.c (_initialize_tui_interp): Add a
> command_loop_proc to interp_procs.
s,gdb/,, in all the above.
OK.
Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2013-09-05 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 17:00 Andrew Burgess
2013-09-05 17:13 ` Pedro Alves [this message]
2013-09-06 8:56 ` Andrew Burgess
2013-09-05 17:14 ` Stan Shebs
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=5228BBB9.4020904@redhat.com \
--to=palves@redhat.com \
--cc=aburgess@broadcom.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