From: Adam Jocksch <ajocksch@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: fhpd commands extended to include displays
Date: Mon, 16 Jul 2007 15:42:00 -0000 [thread overview]
Message-ID: <469B91E6.4050507@redhat.com> (raw)
As of this morning, the enable, disable, delete, and actionpoints
commands have all be extended to work with displays as well as
breakpoints. They also now accept all the parameters specified by the
hpd spec: -enabled, -disabled, -break, -watch, -barrier along with a new
-display option.
Do we want to have somewhere to document the extensions to the hpd spec
that we decide to implement in frysk? (i.e. the display command).
Adam
ChangeLogs:
frysk-core/frysk/rt:
2007-07-16 Adam Jocksch <ajocksch@redhat.com>
* DeleteCommand.java (handle): Now parses the correct parameters
as per the hpd spec.
* DisableCommand.java (handle): Simplified the argument parsing
logic.
* EnableCommand.java (handle): Ditto.
2007-07-11 Adam Jocksch <ajocksch@redhat.com>
* ActionsCommand.java (handle): Now only prints out section
headers if there's something in that section.
* DisableCommand.java (handle): Now accepts all arguments as
specified in the hpd spec.
* EnableCommand.java (handle): Ditto.
* DeleteCommand.java: Reformatted.
(handle): Now deletes displays as well as breakpoints.
* DisableCommand.java: Reformatted.
(handle): Extended to disable displays as well.
* EnableCommand.java: Reformatted.
(handle): Extended to enable displays as well.
frysk-core/frysk/rt:
2007-07-16 Adam Jocksch <ajocksch@redhat.com>
* DisplayManager.java (DisplayMap): Added toString method for debugging
purposes.
2007-07-11 Adam Jockchch <ajocksch@redhat.com>
* UpdatingDisplayValue.java (enabled): Is now a no-op if already
enabled.
(disabled): Is now a no-op if already disabled.
* DisplayManager.java (deleteDisplay): Fixed bug where display was
not being removed from one of the maps.
* DisplayManager.java: Reformatted.
(getDisplay): Added.
* UpdatingDisplayValue.java: Reformatted.
(disable): No longer tells the SteppingEngine to continue.
next reply other threads:[~2007-07-16 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 15:42 Adam Jocksch [this message]
2007-07-19 4:13 ` Stan Cox
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=469B91E6.4050507@redhat.com \
--to=ajocksch@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).