public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: mcvet@sourceware.org
To: frysk-cvs@sourceware.org
Subject: frysk-core/frysk gui/srcwin/ChangeLog gui/srcw ...
Date: Tue, 19 Jun 2007 14:55:00 -0000	[thread overview]
Message-ID: <20070619145506.13965.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/frysk
Module name:	frysk-core
Changes by:	mcvet@sourceware.org	2007-06-19 14:55:06

Modified files:
	frysk/gui/srcwin: ChangeLog SourceWindow.java 
	frysk/cli/hpd  : CLI.java ChangeLog 
	frysk/rt       : SteppingEngine.java ChangeLog 
	                 TestSteppingEngine.java TestStepping.java 
	frysk/gui/disassembler: DisassemblyWindow.java 
	frysk/gui      : ChangeLog 
	frysk/gui/memory: MemoryWindow.java 
	frysk/gui/register: RegisterWindow.java 
	frysk/stack    : ChangeLog TestStackBacktrace.java 

Log message:
	frysk-core/frysk/rt:
	2007-06-19  Mike Cvet  <mcvet@redhat.com>
	
	* SteppingEngine.java (SteppingObserver.updateExecuted): Instead of
	notifying Observers with Task argument, use TaskStepEngine instead.
	(SteppingEngine.notifyNotBlocked): Now takes TaskStepEngine parameter.
	(SteppingEngine.notifyStopped): Removed.
	(SteppingEngine.notifyTask): Removed.
	(stepInstruction): Update logic for calling
	SteppingEngine.notifyNotBlocked with TaskStepEngine parameter.
	(stepLine): Ditto.
	(setUp): Ditto.
	(stepAdvance): Ditto.
	(stepNextInstruction): Ditto.
	(stepOver): Ditto.
	(stepOut): Ditto.
	(continueExecution): Ditto.
	(executeTasks): Ditto.
	* TestStepping.java (LockObserver.update): Updated logic to expect
	TaskStepEngine parameter from Observable, rather than Task or null
	Objects.
	* TestSteppingEngine.java (testLineStepping): Added some cleanup code.
	(setUpTest): Update breakpoint test with new TaskStepEngine.
	(LockObserver.update): Updated logic to expect TaskStepEngine parameter
	instead of null or Task objects.
	
	frysk-core/frysk/stacks:
	2007-06-19  Mike Cvet  <mcvet@redhat.com>
	
	* TestStackBactrace.java (LockObserver.update): Expects TaskStepEngine
	parameter instead of null or Task objects.
	
	frysk-core/frysk/cli/hpd:
	2007-06-19  Mike Cvet  <mcvet@redhat.com>
	
	* CLI.java (SteppingObserver.update): Updated to expect TaskStepEngine
	parameter instead of null or Task objects.
	
	frysk-gui/frysk/gui/srcwin:
	2007-06-19  Mike Cvet  <mcvet@redhat.com>
	
	* SourceWindow.java (LockObserver.update): Removed call to
	SteppingEngine.notifyStopped. Updated to expect TaskStepEngine parameter
	rather than null or Task objects.
	
	frysk-gui/frysk/gui:
	2007-06-19  Mike Cvet  <mcvet@redhat.com>
	
	* disassembler/DisassemblyWindow.java (LockObserver.update): Now
	expects TaskStepEngine parameter rather than null or Task object.
	* memory/MemoryWindow.java (LockObserver.update): Ditto.
	* register/RegisterWindow.java (LockObserver.update): Ditto.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/ChangeLog.diff?cvsroot=frysk&r1=1.488&r2=1.489
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/SourceWindow.java.diff?cvsroot=frysk&r1=1.256&r2=1.257
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/cli/hpd/CLI.java.diff?cvsroot=frysk&r1=1.87&r2=1.88
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/cli/hpd/ChangeLog.diff?cvsroot=frysk&r1=1.9&r2=1.10
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/SteppingEngine.java.diff?cvsroot=frysk&r1=1.27&r2=1.28
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/ChangeLog.diff?cvsroot=frysk&r1=1.284&r2=1.285
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/TestSteppingEngine.java.diff?cvsroot=frysk&r1=1.19&r2=1.20
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/rt/TestStepping.java.diff?cvsroot=frysk&r1=1.31&r2=1.32
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/disassembler/DisassemblyWindow.java.diff?cvsroot=frysk&r1=1.22&r2=1.23
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/ChangeLog.diff?cvsroot=frysk&r1=1.530&r2=1.531
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/memory/MemoryWindow.java.diff?cvsroot=frysk&r1=1.35&r2=1.36
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/register/RegisterWindow.java.diff?cvsroot=frysk&r1=1.36&r2=1.37
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/stack/ChangeLog.diff?cvsroot=frysk&r1=1.9&r2=1.10
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-core/frysk/stack/TestStackBacktrace.java.diff?cvsroot=frysk&r1=1.3&r2=1.4


             reply	other threads:[~2007-06-19 14:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 14:55 mcvet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-09 17:47 mcvet
2007-05-10 20:16 mcvet
2007-04-23 19:34 mcvet
2007-04-23 15:57 mcvet
2007-04-10 19:45 mcvet
2007-04-08  5:14 mcvet
2007-03-16 15:26 mcvet
2007-03-12 20:54 mcvet
2007-03-09 19:19 mcvet
2007-03-08 20:42 mcvet
2007-03-02 15:48 mcvet
2007-02-22 22:12 mcvet
2007-02-20 23:25 mcvet
2007-02-19 21:32 mcvet
2007-02-16 15:15 mcvet
2007-02-15 18:45 mcvet

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=20070619145506.13965.qmail@sourceware.org \
    --to=mcvet@sourceware.org \
    --cc=frysk-cvs@sourceware.org \
    --cc=frysk@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).