Method, apparatus, device, storage medium, and program product for identifying an abnormal component

1 . A method for identifying an abnormal component, comprising:

in response to an exception event occurring during execution of an application program on a terminal device, automatically acquiring, by a processor of the terminal device, exception log information for the application program, wherein the exception log information is automatically generated during the execution of the application program;

automatically performing symbol parsing, by the processor of the terminal device, based on exception address information in the exception log information and a first mapping relationship, to obtain symbolic information of the exception address information, wherein the symbolic information comprises index information, and the first mapping relationship comprises a mapping relationship between address information and symbolic information that is obtained based on a predetermined symbol table;

automatically obtaining, by the processor of the terminal device, a compilation path of the exception log information based on the index information in the symbolic information and a second mapping relationship, wherein the second mapping relationship comprises a mapping relationship between index information and compilation path that is obtained based on the predetermined symbol table, and a one-to-one correspondence between the index information and the compilation path;

automatically determining, by the processor of the terminal device, the abnormal component based on the compilation path and predetermined configuration information indicating a location of component information in the compilation path;

automatically determining, by the processor of the terminal device, whether a dynamic library name of the abnormal component matches a dynamic library name comprised in component configuration information; and

in response to the dynamic library name of the abnormal component matching the dynamic library name comprised in the component configuration information, automatically assigning, by the processor of the terminal device, information of the abnormal component to a component space according to a dynamic library assignment rule, the component space comprising one of a plurality of SDK spaces with registered names of components, wherein a component assigned to the component space is to be maintained.

2 . The method of claim 1 , wherein determining the abnormal component based on the compilation path and the predetermined configuration information indicating the location of component information in the compilation path comprises:

determining a pod name of the exception log information based on the compilation path;

determining component information in the compilation path based on the pod name and the predetermined configuration information; and

determining the abnormal component based on the component information.

3 . The method of claim 2 , wherein determining the pod name of the exception log information based on the compilation path comprises:

determining whether the compilation path comprises a first predetermined string; and

in response to the compilation path comprising the first predetermined string, determining a first string following the predetermined string in the compilation path to be the pod name.

4 . The method of claim 2 , wherein determining the pod name of the exception log information based on the compilation path comprises:

determining whether the compilation path comprises a first predetermined string; and

in response to the compilation path not comprising the first predetermined string, determining a second string at the beginning of the compilation path to be the pod name.

5 . The method of claim 2 , wherein determining the pod name of the exception log information based on the compilation path comprises:

determining whether the compilation path comprises a second predetermined string; and

in response to the compilation path comprising the second predetermined string, determining a predetermined pod name corresponding to the second predetermined string in a third mapping relationship to be the pod name of the exception log information.

6 . The method of claim 1 , wherein determining the abnormal component based on the compilation path and the predetermined configuration information comprises:

determining a feature of the abnormal component based on the pod name and the predetermined configuration information; and

determining a name of the abnormal component based on the feature of the abnormal component, so as to determine the abnormal component.

7 . The method of claim 1 , wherein the exception log information comprises a name of an abnormal dynamic library, and the method further comprises:

acquiring a name of a component dynamic library corresponding to a component in the application program;

determining whether the name of the component dynamic library matches the name of the abnormal dynamic library; and

in response to the name of the component dynamic library matching the name of the abnormal dynamic library, determining a component corresponding to the name of the component dynamic library to be the abnormal component.

8 . The method of claim 1 , further comprising:

acquiring component configuration information determined by a developer;

determining whether the abnormal component matches the component configuration information; and

in response to the abnormal component matching the component configuration information, sending information of the abnormal component to the developer.

9 . An electronic device comprising a memory, a processor, and a computer program that is stored on the memory and executable on the processor, the electronic device being a terminal device, wherein the processor, when running the computer program, performs acts comprising:

in response to an exception event occurring during execution of an application program on the terminal device, automatically acquiring, by the processor of the terminal device, exception log information for the application program, wherein the exception log information is automatically generated during the execution of the application program;

automatically performing symbol parsing, by the processor of the terminal device, based on exception address information in the exception log information and a first mapping relationship, to obtain symbolic information of the exception address information, wherein the symbolic information comprises index information, and the first mapping relationship comprises a mapping relationship between address information and symbolic information that is obtained based on a predetermined symbol table;

automatically obtaining, by the processor of the terminal device, a compilation path of the exception log information based on the index information in the symbolic information and a second mapping relationship, wherein the second mapping relationship comprises a mapping relationship between index information and compilation path that is obtained based on the predetermined symbol table, and a one-to-one correspondence between the index information and the compilation path;

automatically determining, by the processor of the terminal device, an abnormal component based on the compilation path and predetermined configuration information indicating a location of component information in the compilation path;

automatically determining, by the processor of the terminal device, whether a dynamic library name of the abnormal component matches a dynamic library name comprised in component configuration information; and

in response to the dynamic library name of the abnormal component matching the dynamic library name comprised in the component configuration information, automatically assigning, by the processor of the terminal device, information of the abnormal component to a component space according to a dynamic library assignment rule, the component space comprising one of a plurality of SDK spaces with registered names of components, wherein a component assigned to the component space is to be maintained.

10 . The electronic device of claim 9 , wherein determining the abnormal component based on the compilation path and the predetermined configuration information indicating the location of component information in the compilation path comprises:

determining a pod name of the exception log information based on the compilation path;

determining component information in the compilation path based on the pod name and the predetermined configuration information; and

determining the abnormal component based on the component information.

11 . The electronic device of claim 10 , wherein determining the pod name of the exception log information based on the compilation path comprises:

determining whether the compilation path comprises a first predetermined string; and

in response to the compilation path comprising the first predetermined string, determining a first string following the predetermined string in the compilation path to be the pod name.

12 . The electronic device of claim 10 , wherein determining the pod name of the exception log information based on the compilation path comprises:

determining whether the compilation path comprises a first predetermined string; and

in response to the compilation path not comprising the first predetermined string, determining a second string at the beginning of the compilation path to be the pod name.

13 . The electronic device of claim 10 , wherein determining the pod name of the exception log information based on the compilation path comprises:

determining whether the compilation path comprises a second predetermined string; and

in response to the compilation path comprising the second predetermined string, determining a predetermined pod name corresponding to the second predetermined string in a third mapping relationship to be the pod name of the exception log information.

14 . The electronic device of claim 9 , wherein determining the abnormal component based on the compilation path and the predetermined configuration information comprises:

determining a feature of the abnormal component based on the pod name and the predetermined configuration information; and

determining a name of the abnormal component based on the feature of the abnormal component, so as to determine the abnormal component.

15 . The electronic device of claim 9 , wherein the exception log information comprises a name of an abnormal dynamic library, and the acts further comprises:

acquiring a name of a component dynamic library corresponding to a component in the application program;

determining whether the name of the component dynamic library matches the name of the abnormal dynamic library; and

in response to the name of the component dynamic library matching the name of the abnormal dynamic library, determining a component corresponding to the name of the component dynamic library to be the abnormal component.

16 . The electronic device of claim 9 , further comprising:

acquiring component configuration information determined by a developer;

determining whether the abnormal component matches the component configuration information; and

in response to the abnormal component matching the component configuration information, sending information of the abnormal component to the developer.

17 . A non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions for causing a computer to perform acts comprising:

in response to an exception event occurring during execution of an application program on a terminal device, automatically acquiring, by a processor of the terminal device, exception log information for the application program, wherein the exception log information is automatically generated during the execution of the application program;

automatically performing symbol parsing, by the processor of the terminal device, based on exception address information in the exception log information and a first mapping relationship, to obtain symbolic information of the exception address information, wherein the symbolic information comprises index information, and the first mapping relationship comprises a mapping relationship between address information and symbolic information that is obtained based on a predetermined symbol table;

automatically obtaining, by the processor of the terminal device, a compilation path of the exception log information based on the index information in the symbolic information and a second mapping relationship, wherein the second mapping relationship comprises a mapping relationship between index information and compilation path that is obtained based on the predetermined symbol table, and a one-to-one correspondence between the index information and the compilation path;

automatically determining, by the processor of the terminal device, an abnormal component based on the compilation path and predetermined configuration information indicating a location of component information in the compilation path;

automatically determining, by the processor of the terminal device, whether a dynamic library name of the abnormal component matches a dynamic library name comprised in component configuration information; and

in response to the dynamic library name of the abnormal component matching the dynamic library name comprised in the component configuration information, automatically assigning, by the processor of the terminal device, information of the abnormal component to a component space according to a dynamic library assignment rule, the component space comprising one of a plurality of SDK spaces with registered names of components, wherein a component assigned to the component space is to be maintained.

18 . The non-transitory computer-readable storage medium of claim 17 , wherein determining the abnormal component based on the compilation path and the predetermined configuration information indicating the location of component information in the compilation path comprises:

determining a pod name of the exception log information based on the compilation path;

determining component information in the compilation path based on the pod name and the predetermined configuration information; and

determining the abnormal component based on the component information.

19 . The non-transitory computer-readable storage medium of claim 17 , wherein determining the abnormal component based on the compilation path and the predetermined configuration information comprises:

determining a feature of the abnormal component based on the pod name and the predetermined configuration information; and

determining a name of the abnormal component based on the feature of the abnormal component, so as to determine the abnormal component.

20 . The non-transitory computer-readable storage medium of claim 17 , wherein the exception log information comprises a name of an abnormal dynamic library, and the acts further comprises:

acquiring a name of a component dynamic library corresponding to a component in the application program;

determining whether the name of the component dynamic library matches the name of the abnormal dynamic library; and

in response to the name of the component dynamic library matching the name of the abnormal dynamic library, determining a component corresponding to the name of the component dynamic library to be the abnormal component.