From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [vxworks 02/14] New command_post observer.
Date: Mon, 26 Apr 2010 18:51:00 -0000 [thread overview]
Message-ID: <m3aasqnj4b.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1272210447-13895-3-git-send-email-brobecker@adacore.com> (Joel Brobecker's message of "Sun, 25 Apr 2010 11:47:15 -0400")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> The problem is that we cannot just print a message everytime the PD
Joel> gets switched, because many commands result in a temporary switch of
Joel> partition.
Joel> The way we solved this is by remembering the PD ID before we issued
Joel> the last command. At the end of a command execution, if the PD ID
Joel> changed, then we write a notification...
Joel> This patch introduces an observer (command_post) that gets triggered
Joel> at the end of a command execution...
There are a lot of calls to execute_command that occur in batch-like
places. For example, this is called from Python, I think it is called
from "commands" scripts and "define" scripts, etc.
So if your goal is to have it just emit info at some stopping point, it
seems to me that it would be better to have an observer just before a
prompt is emitted.
I didn't read every patch in detail, so I didn't see where this is used.
Maybe the above doesn't matter.
Tom
next prev parent reply other threads:[~2010-04-26 18:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 15:47 Adding support for VxWorks target Joel Brobecker
2010-04-25 15:47 ` [vxworks 01/14] Some ada-lang/ada-tasks routines needed by the " Joel Brobecker
2010-04-25 15:48 ` [vxworks 08/14] Partition support Joel Brobecker
2010-04-25 15:48 ` [vxworks 11/14] WTX-TCL support module Joel Brobecker
2010-04-25 15:48 ` [vxworks 13/14] Add tdep files for x86 and powerpc Joel Brobecker
2010-04-25 20:45 ` Mark Kettenis
2010-04-26 16:41 ` Joel Brobecker
2010-04-25 15:48 ` [vxworks 09/14] remote-wtx-hw / register fetch/store support Joel Brobecker
2010-04-25 15:48 ` [vxworks 10/14] Add new "wtx" target Joel Brobecker
2010-04-25 15:48 ` [vxworks 14/14] Configury and Makefile updates for VxWorks Joel Brobecker
2010-04-25 15:48 ` [vxworks 02/14] New command_post observer Joel Brobecker
2010-04-26 18:51 ` Tom Tromey [this message]
2010-04-27 14:22 ` Joel Brobecker
2010-04-27 17:16 ` Tom Tromey
2010-04-25 15:48 ` [vxworks 03/14] New module remote-wtx-utils Joel Brobecker
2010-04-26 18:55 ` Tom Tromey
2010-04-27 16:27 ` Joel Brobecker
2010-04-25 15:56 ` [vxworks 12/14] Add support for VxWorks 6 Joel Brobecker
2010-04-25 15:56 ` [vxworks 05/14] Add options to control Vxworks related settings Joel Brobecker
2010-05-04 15:25 ` Joel Brobecker
2010-04-25 15:56 ` [vxworks 06/14] VxWorks breakpoint-handling module Joel Brobecker
2010-04-25 15:56 ` [vxworks 07/14] "multi-tasks-mode" support Joel Brobecker
2010-04-25 16:01 ` [vxworks 04/14] remote-wtxapi: The WTX API abstraction layer Joel Brobecker
2010-05-04 14:58 ` Adding support for VxWorks target Joel Brobecker
2010-05-04 15:43 ` Stan Shebs
2010-05-04 18:30 ` one big unit or several smaller units? (was: "Re: Adding support for VxWorks target") Joel Brobecker
2010-11-25 0:53 ` Adding support for VxWorks target Joel Brobecker
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=m3aasqnj4b.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).