PATHFINDER

Course Information

Group Information

Project Description

Development Environment

Developmental Stages

• Preliminary Design
  
• Preliminary Design Presentation
  
• Detailed Design
  
• First DFDs
  
• Second DFDs
  

References

Future Improvements

Overall Project Difficulties

A Few Words from the Group

User's Guide

Feedback

Execute

1. PATHFINDER should run the a.out
2. PATHFINDER will start the Event Log
3. Program execution will pause after each event so each event can be written to the Event Log
4. Wrapper Function will recognize system calls, place the necessary information the Event Log needs
   into a queue, do the system call, and return control to PATHFINDER
5. Wrapper Function will contain all the system calls that were discussed in class except for setjmp() and longjmp()
6. The main program will get the information the Wrapper Function placed in the queue and place it in the Event Log

1. The Event Log will be a data file that will contain all the events that took place during the execution of
   the program.
2. The Event Log will contain the following fields: user name, program name, process name, process id,
   system call, predecessor, successor, start and end time of process, LOC, errors, Kernel ID key
3. The Event Log will be overwritten every time PATHFINDER is ran
4. The Event Log will be hard coded "Event_Log.dat"