Here are some basic information of an old version of OS. First, the system only has 2 segments (segment O for code and a growing heap, segment 1 for a negatively-growing stack). The virtual address space size is only 128 bytes, and there is only 1K of physical memory. Therefore, code and heap together starts from O in the virtual address space and stack starts from 127 in the virtual address space. We now have one set of traces from an old program. In particular, the traces tell you which virtual address was accessed in byte), and then whether or not the access was valid or not (i.e., a segmentation violation). If valid, the physical address is reported. Oddly enough, programs in this OS are allowed to keep running after memory-access violations, and thus we have a long trace that continues even after such a violation occurred. Here is the trace: VA: 108 Valid in SEG1: 1004 VA: 29 Valid in SEGO: 541 VA: 80 Segmentation violation (SEG1) VA: 30 Segmentation violation (SEGO) VA: 88 Valid in SEG1: 984 VA: 97 Valid in SEG1: 993 VA: 53 Segmentation violation (SEGO) VA: 33 Segmentation violation (SEGO) VA: 100 Valid in SEG1: 996 VA: 61 Segmentation violation (SEGO) VA: 12 Valid in SEGO: 524 VA: 5 Valid in SEGO: 517 VA:47 Segmentation violation (SEGO) Now please use the trace to determine the base and bounds for each segment. The base and bounds can be an exact value or in a range (a format like 10