A method for information processing, comprising: detecting whether a target OAT file corresponding to a target DEX file that an application relies on is missing, in response to a start control instruction for the application detected; detecting existence of a backup target OAT file when the target OAT file is missing; determining a hard-link file configured to backup the target OAT file and reading the target OAT file from the hard-link file, when the backup target OAT file exists; verifying validity of the target OAT file; loading the target OAT file when the target OAT file is valid; obtaining and loading the target OAT file by compiling the target DEX file, when the backup target OAT file does not exist; and establishing the hard-link file configured to backup the target OAT file and storing the target OAT file into the hard-link file corresponding to the target OAT file; wherein the verifying validity of the target OAT file comprises: determining whether the number of offset arrays of the target OAT file is equal to that of data types of the target DEX file; determining that the target OAT file is valid based on a determination that the number of the offset arrays of the target OAT file is equal to that of the data types of the target DEX file; and determining that the target OAT file is invalid based on a determination that the number of the offset arrays of the target OAT file is not equal to that of the data types of the target DEX file. detecting whether a target OAT file corresponding to a target DEX file that an application relies on is missing, in response to a start control instruction for the application detected; detecting existence of a backup target OAT file when the target OAT file is missing; determining a hard-link file configured to backup the target OAT file and reading the target OAT file from the hard-link file, when the backup target OAT file exists; verifying validity of the target OAT file; loading the target OAT file when the target OAT file is valid; obtaining and loading the target OAT file by compiling the target DEX file, when the backup target OAT file does not exist; and establishing the hard-link file configured to backup the target OAT file and storing the target OAT file into the hard-link file corresponding to the target OAT file; wherein the verifying validity of the target OAT file comprises: determining whether the number of offset arrays of the target OAT file is equal to that of data types of the target DEX file; determining that the target OAT file is valid based on a determination that the number of the offset arrays of the target OAT file is equal to that of the data types of the target DEX file; and determining that the target OAT file is invalid based on a determination that the number of the offset arrays of the target OAT file is not equal to that of the data types of the target DEX file. determining whether the number of offset arrays of the target OAT file is equal to that of data types of the target DEX file; determining that the target OAT file is valid based on a determination that the number of the offset arrays of the target OAT file is equal to that of the data types of the target DEX file; and determining that the target OAT file is invalid based on a determination that the number of the offset arrays of the target OAT file is not equal to that of the data types of the target DEX file. <EOS>