UniMod-1.3-Debugger

From UniMod Wiki

ally mcbeal video mastercard priceless videos ozzie smith video river raider 2 crack alexender the movie tin cup shoreline theater mountain view ca juggalo anthem netscape aol music videos movie4s unicel mp3 ringtone sitemap web host listing home magazine wedding invitation paper renee jaquith jpeghunter porno www.afl.com online video player partition magic 8 serial number restaurant mountain view missouri institutionnel illinois dot drivers licence edmonton movieline hollywood life magazine janet jackson video super bowl 2004 address book paris hilton online ii magic movie name ecapital corporation replica designer handbags leaving on a jet plane wav domain s video to rca converter cable dot testing programs sheepskin rugs rolrelcoacta

Contents 1 UniMod Runtime Engine 2 Thread Models 3 Application-side Debugger Model 4 Eclipse-side Debugger Model

UniMod Runtime Engine

UniMod runtime engine class diagram:

Thread Models

UniMod runtime engine supports two thread models:

• Strict. Thread that comes with Event is used for event processing. Caller of method EventHandler.handle() is blocked until the end of Event processing. If more then one Event will be posted concurrently, their thread will not be joined, so there will be more then one thread processing Event against the same engine. It’s not bad and rather good for developing Web application that works inside Servlet container. See Messenger Web for more details;
• Queued. Event queue exists (see activity diagram below). Event dispatcher thread checks for new Event in queue and if there is one – starts its processing. It’s guaranteed that Events are dispatched from queue one-by-one, so in any time only one Event is being processed against same engine. Caller thread is not blocked. It’s not allowed to change in-memory model after StateMachineEngine created.

Application-side Debugger Model

Application-side debugger is implemented using UniMod itself. Connectivity diagram:

Statemachine A1 (main):

Statemachine A2 (breakpoint management):

Target UniMod model is being debugged using debugger which is developed using UniMod itself. The following picture illustrates how all this stuff work.

Eclipse-side Debugger Model

Eclipse-side debugger is implemented using UniMod itself.
Connectivity diagram:

Statemachine A1 (main):

Statemachine A2 (breakpoint management):