If GDB or shared library integrity check caused detection of errors then further use of the present GDB is insecure. In this situation you can either return to a backup copy (supposing that the user creates backup copies regularly checking their integrity beforehand) or perform repair operation by selecting the menu command GDB+Repair. This command will start the integrity repair wizard (figure 6-9)
Figure 6-9. Integrity repair wizard
On the first page of the wizard the user has to select GDB or shared library for repair.
If the box Use change file is checked, the data from the change file will be also included into the initial data which is subject to repair. The result of repair is always recorded into the main GDB or shared library files and the used change file is removed.
It is also possible to select a file for recording the repair report into it. For report files on repair the system uses RPR extension.
The checked box Detailed error information determines if the data about errors of repairing particular features and records will be shown or not. If the box is cleared only the data about errors in GDB components structure will be given.
After pushing the buttons Next and Repair the system makes an attempt to eliminate data corruption. As a rule, the system is able to do this, however, during repair a part of corrupted data may be lost. After performing the operation the system displays a message “The repair completed successfully” or “Repair is impossible”.
 |  |
