--------------------------------------- ISVis: Interaction Scenario Visualizer --------------------------------------- VERSION: 1.0 DATE: Dec 30, 1997 List of Files ------------- COPYRIGHT README bin/ isvis isvis_tracelib.o isv_instr sbfilesin sbstatic doc/ isvis_userguide.html isvis_logo.jpeg isvis.gif main_big.gif scenario_big.gif include/ event_writer.H src/ Makefile actor.H actor_list_view.H disk_file.H event.H event_reader.H global_state.H hash.H instrumentor.H interaction.H io_shell.H main_view.H mural.H program_model.H scenario.H scenario_view.H static_analyzer.H static_info.H trace.H trace_analyzer.H view.H view_manager.H xapp.H actor.C actor_list_view.C disk_file.C event.C event_reader.C event_writer.C hash.C instrumentor.C interaction.C io_shell.C main_view.C mural.C program_model.C scenario.C scenario_view.C static_analyzer.C static_info.C trace.C trace_analyzer.C view.C view_manager.C xapp.C /tutorial boxscen1.jpg dfs.staticinfo dfs.trace dfs.traceinfo isvis_tut.html isvis_tut2.html isvis_tut3.html isvis_tut4.html mainscr1.jpg scenv.jpg /tutorial/Polka {source files for use in tutorial} Installation ------------ Platform Requirements: Solaris2.5+, SunOS 4.1.x, IRIX 5.2+ X11R5 Motif 1.1+ RogueWave tools.h++ 1) obtain the compressed ISVis tar file 2) create a home directory for ISVis on your system 3) place the compressed ISVis tar file in the directory from (2) 4) uncompress the ISVis tar file: uncompress 5) extract the tar archive: tar xvf This should create the subdirectories /bin, /include, and /src containing the files listed above. (Note that /bin/isvis and /bin/isvis_tracelib.o are not created until compilation) 6) edit the /src/Makefile as follows: a) change the ISVIS_HOME variable to reflect the directory in (2) b) uncomment the appropriate OS dependent flags for your OS, and make any modifications to the compiler, X Windows, and Motif include and library paths as appropriate c) make sure the OS dependent flags for other OS's are commented out using a pound sign (#) 7) cd to the /src directory and type make depend (ignore any strange messages resulting from the RogueWave tools.h++. Specifically, this step may issue control characters to your screen.) 8) compile ISVis by typing make This will create the executable bin/isvis and the tracing library bin/isvis_tracelib.o (You will see a large number of warning messages. These are an artifact of interfacing with RogueWave tools.h++ and are expected.) 9) add the ISVis bin directory to your shell path Documentation ------------- HTML user guide is included as doc/isvis_userguide.html. Tutorial -------- Check out the ISVis tutorial by Bob Waters, starting with tutorial/isvis_tut.html. Contact Info ------------ Bug Reporting isvis-bugs@cc.gatech.edu General Morale Tool Support morale_support@cc.gatech.edu Known Bugs ---------- MAJOR: Running Demo rlogin to krel, display on Peachtree (dfs.trace all actors loaded) Just had completed tutorial step with creating initial box pattern with initial Intercepts interaction being entered. Gave command 'r' for reverse direction. Pause, windows quit updating. Resized main screen and core dump. Last few outputs: prog model: scenario Bound Rect loaded prog model: scenario Box Pattern loaded set up table with 2 prog model: interaction loaded Segmentation Fault (core dumped) Try to repeat. If I deliberaty misspell interaction what happens? Could not duplicate, tried misspelling, aborting then accepting etc. Could not cause a repeat! ******************************************************************************* ******************************************************************************* MAJOR: Running demo, any conditions, try to open a session file after any trace file or other session file has been opened results in a core dump. Last few messages: prog model: interaction loaded prog model: interaction loaded prog model: interaction loaded prog model: interaction loaded prog model: scenario dfs.trace loaded Segmentation Fault (core dumped) ******************************************************************************* ******************************************************************************* MINOR: If incorrect filename given to open a session file, no feedback is given that file not found or file failed to open. ******************************************************************************* ******************************************************************************* MAJOR: While using dfsFinal.session demonstration file, with 2 small scenarios opened, opened the trace file scenario, closed it and opened Copy 1. At that point ISVis failed. Last Output: ISVis Interaction Scenario Visualizer gui v0.4 program = Polka/dfs set up table with 3 set up table with 3 set up table with 6 set up table with 4 set up table with 115 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Resource id in failed request: 0x4c00266 Serial number of failed request: 12572 Current serial number in output stream: 12770 Attempt to repeat failure by opening trace file, immediately closing and opening Copy did not crash, but opening several scenarios, then opening and closing Copy 1 caused repeat failure: set up table with 3 set up table with 115 X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 62 (X_CopyArea) Resource id in failed request: 0x4c002be Serial number of failed request: 59786 Current serial number in output stream: 59790 Attempt to narrow failure. Appears to be that if you open a second copy of a scenario, then close either view, and attempt to open any other scenario, isvis will fail with some error message. Seems to cause the window manager to die: set up table with 115 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 2 (X_ChangeWindowAttributes) Resource id in failed request: 0x4c00159 Serial number of failed request: 4211 Current serial number in output stream: 4279 Corrective Action??? possibly keep track of current scenarios opened, and not allow user to view more than one copy of the scenario. ******************************************************************************* ******************************************************************************* MAJOR: While running ISVis demo, on SPARC 20 (krel), during scenario copy of default trace, program faiactions when th