CN111026575B - Abnormality processing method and device and electronic equipment - Google Patents
Abnormality processing method and device and electronic equipment Download PDFInfo
- Publication number
- CN111026575B CN111026575B CN201911201822.5A CN201911201822A CN111026575B CN 111026575 B CN111026575 B CN 111026575B CN 201911201822 A CN201911201822 A CN 201911201822A CN 111026575 B CN111026575 B CN 111026575B
- Authority
- CN
- China
- Prior art keywords
- component
- abnormality
- information
- target
- page
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000005856 abnormality Effects 0.000 title claims abstract description 146
- 238000003672 processing method Methods 0.000 title description 3
- 230000002159 abnormal effect Effects 0.000 claims abstract description 56
- 238000000034 method Methods 0.000 claims abstract description 43
- 238000004806 packaging method and process Methods 0.000 claims abstract description 15
- 238000012545 processing Methods 0.000 claims abstract description 11
- 238000004891 communication Methods 0.000 claims description 18
- 230000007246 mechanism Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 8
- 238000002347 injection Methods 0.000 claims description 8
- 239000007924 injection Substances 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 abstract description 7
- 230000006870 function Effects 0.000 description 11
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 5
- 238000007906 compression Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006835 compression Effects 0.000 description 3
- 239000000243 solution Substances 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0718—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in an object-oriented system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides an exception handling method, an exception handling device and electronic equipment, wherein the method comprises the following steps: when the component of the target page is abnormal, capturing target abnormality in the abnormal component; packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information; and sending the target abnormal information to a background server. By packaging the component information into the anomaly information, a developer can determine the specific component with the anomaly through the component information without analyzing and processing each captured anomaly, so that the efficiency of locating the component-level source of the anomaly is improved, and the analysis time and cost are saved.
Description
Technical Field
The present invention relates to the field of front-end development technologies, and in particular, to an exception handling method and apparatus, and an electronic device.
Background
Based on the modular development model of the component, the inside of the page will present the component tree structure, and thus Java Script error exceptions inside the component will often cause the page or component to crash.
In the prior art, when a page is abnormal and crashed, original abnormal information can be usually only positioned to report errors of a page level, a specific abnormal component cannot be determined quickly, a developer is required to analyze and process the original abnormal information in a large amount to determine the source of the abnormal component level, and the time and the labor are consumed.
It can be seen that in the prior art, locating the component level source of anomalies is inefficient.
Disclosure of Invention
The embodiment of the invention aims to provide an exception handling method, an exception handling device and electronic equipment, so as to quickly locate an exception component level source. The specific technical scheme is as follows:
in a first aspect of the present invention, there is provided an exception handling method, including:
when the component of the target page is abnormal, capturing target abnormality in the abnormal component;
packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information;
and sending the target abnormal information to a background server.
In a second aspect of the present invention, there is also provided an exception handling apparatus, including:
the capturing module is used for capturing target abnormality in the abnormal component when the abnormal component of the target page occurs;
the injection module is used for encapsulating the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information;
and the sending module is used for sending the target abnormal information to a background server.
In a third aspect of the present invention, there is also provided an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the steps of the method in the first aspect of the embodiment of the invention when executing the program stored in the memory.
In yet another aspect of the present invention, there is also provided a computer readable storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform any of the above-described exception handling methods.
In yet another aspect of the invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the above-described exception handling methods.
According to the exception handling method, the exception handling device and the electronic equipment provided by the embodiment of the invention, when an exception occurs in a component of a target page, the target exception is captured in the abnormal component; packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information; and sending the target abnormal information to a background server. By packaging the component information into the anomaly information, a developer can determine the specific component with the anomaly through the component information without analyzing and processing each captured anomaly, so that the efficiency of locating the component-level source of the anomaly is improved, and the analysis time and cost are saved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
FIG. 1 is a flowchart of an exception handling method according to an embodiment of the present invention;
FIG. 2 is a flowchart of another exception handling method according to an embodiment of the present invention;
FIG. 3 is a block diagram of an exception handling apparatus according to an embodiment of the present invention;
FIG. 4 is a block diagram of another exception handling apparatus according to an embodiment of the present invention;
FIG. 5 is a block diagram of an exception handling apparatus according to an embodiment of the present invention;
fig. 6 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.
Example 1
Referring to fig. 1, fig. 1 is a schematic diagram of an exception handling method according to an embodiment of the present invention, where the method may be applied to a front end of a server, and in particular, may be applied to a real, real-Native framework developed by the front end, which is not limited herein.
As shown in fig. 1, the method comprises the steps of:
step 101, capturing target abnormality in an abnormal component when the abnormal component of the target page occurs;
102, packaging component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information;
and step 103, the target abnormal information is sent to a background server.
The code abnormality in the component can cause page abnormality and even crash, but because the online code of the target page is compressed and compiled, the semantically code is completely destroyed to lose readability, and the component tree of the page is huge and complex, the page level error can be usually only detected, the specific component with abnormality can not be rapidly positioned, and the specific code with abnormality can not be rapidly determined.
Based on the modular development model of the component, the online code of the target page will present a component tree structure. Parent-child or sibling relationships exist among the components in the component tree, and the parent-child components and the sibling components can be mutually called and communicated based on calling logic. When a child component crashes or an exception occurs, the exception can be captured by a try/catch function and thrown by a throw function, the thrown exception can be captured by a parent component capable of calling the child component, and so on. When an exception occurs in a component of the target page, the exception may be thrown layer by layer until captured by a certain ancestor component to present exception information.
In the embodiment of the invention, when the component of the target page is abnormal, the target abnormality can be captured in the abnormal component by utilizing the existing abnormality capturing method.
Specifically, in step 101, when an exception occurs in a component of the target page, the exception may be captured by using a try/catch function in the component in which the exception occurs, and thrown out by a throw function, and the target exception may be thrown out layer by layer following the component tree structure, and the exception is presented on the target page. The exception information presented at this time belongs to the original information of the target exception, characterizes the exception itself which occurs, usually presents grammar errors of codes, does not have readable information, and developers cannot acquire detailed information of the exception from the current exception information.
In step 102, the component information of the component in which the abnormality occurs refers to the identification information related to the component, such as the name, attribute, and the like of the component. When an abnormality occurs in a certain component of the target page, the component information of the component with the abnormality can be automatically acquired and packaged into the abnormality information of the target abnormality, so that when the abnormality information packaged with the component information is sent to a background server, a developer can directly and quickly determine the component with the current target abnormality according to the component information, and the efficiency of repairing the abnormality is improved.
The above-mentioned encapsulation of the component information of the component in which the abnormality occurs into the abnormality information of the target abnormality may be understood as: the component information is written as a value in the exception information field, which is not limited herein.
In the embodiment of the invention, when the component of the target page is abnormal, capturing the target abnormality in the abnormal component; packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information; and sending the target abnormal information to a background server. By packaging the component information into the anomaly information, a developer can determine the specific component with the anomaly through the component information without analyzing and processing each captured anomaly, so that the efficiency of locating the component-level source of the anomaly is improved, and the analysis time and cost are saved.
Example two
Referring to fig. 2, fig. 2 is a schematic diagram of another exception handling method according to an embodiment of the present invention, where the method may be applied to a front end of a server, and in particular, may be applied to a real, real-Native framework developed by the front end, which is not limited herein.
As shown in fig. 2, the method comprises the steps of:
step 201, capturing a target abnormality in a first component of a target page according to a preset abnormality capturing mechanism when the first component is abnormal, wherein the first component is any component in the target page;
step 202, processing the target abnormality to generate first abnormality information, wherein the first abnormality information comprises the content and the type of the target abnormality;
step 203, acquiring component information of the first component, wherein the component information of the first component includes a component identifier, a component name and a component position of the first component;
step 204, packaging the component information of the first component in the first abnormal information to generate target abnormal information;
and step 205, the target abnormal information is sent to a background server.
In this embodiment, the first component is any component in the target page, and when an abnormality occurs in the first component of the target page, the target abnormality may be captured in the first component according to a preset abnormality capturing mechanism, where the preset abnormality capturing mechanism may be understood as:
in the development stage, a developer packages the exception capture logic inside each component, only exposes an API (Application Programming Interface, application program interface) to the outside, and the exception capture function can be realized inside each component only by simple configuration parameters, so that the packaged exception capture logic is not compressed and destroyed in the code compression process, and the invasiveness of codes is reduced.
The above-described exception trap logic may be understood as invoking an exception trap function to trap exceptions within the component, such as a try/catch function, a throw function, etc., without limitation.
According to the abnormality capturing mechanism, based on abnormality capturing logic packaged in the first component, the abnormality occurring in the first component is captured by the first component, and the abnormality captured by the first component can correspondingly acquire the component information of the first component, which is equivalent to establishing a one-to-one correspondence between the abnormality and the component in which the abnormality occurs.
In step 202, the captured target anomaly may be processed to generate first anomaly information, the first anomaly information including the content and type of the target anomaly.
The first anomaly information may include content and type of anomaly, and may further include readable information that may reflect the anomaly, such as cause and attribute of anomaly, and is not limited herein.
The first anomaly information is information with readability after the original anomaly information is analyzed and processed. Specifically, the online code loses readability after being compressed, after capturing the target exception, the presented exception information is the unreadable original exception information, in this embodiment, the current original exception information can be processed and arranged into readable exception information according to a conventional analysis processing method, and then a developer does not need to analyze and process the exception again, so that semantic readable exception information can be presented for the developer, analysis time and cost of the developer are reduced, and efficiency of locating component-level sources of the exception is further improved.
In step 203, since the abnormality capturing mechanism is preset, the abnormality occurring in the first component is captured by the first component, so that the component information of the first component can be obtained correspondingly.
Specifically, before the target page is online, that is, before the code of the target page is compressed, the front end of the server can buffer the component information of each component, so that the component information is prevented from being damaged in the process of code compression. After the code is online, when the first component of the target page is abnormal, the component information of the first component can be automatically acquired from the pre-cached component information.
The component information of the first component comprises a component identifier, a component name and a component position of the first component. The component identifier refers to information capable of uniquely identifying the component, and the information can be directly the name of the current component, an ID, a group of numbers or a string of character strings; it may be randomly generated or custom by the developer at the compiling stage, and is not limited in any way. Each component of the target page has a unique component identifier, and a developer can determine a specific component according to the component identifier so as to quickly locate the source of the abnormality.
The component names are used for representing specific functions of the components, such as a network connection component, a data storage component and the like, so that developers can be assisted in locating sources of anomalies, and efficiency is further improved.
The component positions described above are used to characterize the position of the component in the entire page component tree, i.e., the upper and lower level or level reference relationships of the component in the component tree. After the exception is captured, a developer not only determines the component throwing the current exception, but also needs to locate the specific position of the component to check codes in the component so as to process the exception and eliminate the influence caused by the exception. The page codes are many and long, if a specific component is searched in the component tree only through the component identifier or the component name, the time and the energy are high, and according to the component position, namely the calling relation of the component, a developer can be assisted to quickly locate the code blocks of the first component in the component tree, so that the efficiency is further improved.
In step 204, the acquired component information of the first component is encapsulated in the first anomaly information of the currently captured anomaly, and the target anomaly information is generated, which is equivalent to the source of the anomaly injection component. . The first exception information may include a component information field, where the encapsulating the component information of the first component in the first exception information may be understood as: the component information of the first component is written as a value into the component information field, and the specific implementation is not limited herein.
In step 205, the target abnormality information encapsulated with the component information is sent to the background server, and the developer can quickly determine the specific component in which abnormality occurs currently according to the component information.
In this embodiment, at the compiling stage before code compression, the component information of each component is cached, so as to avoid that the component information is damaged by compression and loses readability, after a target page is online, when an abnormality occurs in a certain component of the target page, the abnormality is captured in the current component by using the abnormality capturing logic encapsulated in each component, and meanwhile, the component information of the current component cached in advance is obtained, and is encapsulated into the abnormality information and is uniformly transmitted to a background server, so that a developer does not need to analyze and process the abnormality information any more, the abnormal component information can be determined quickly according to the component information, the efficiency of locating the source of the abnormal component level is further improved, and the analysis time and cost are further saved.
Optionally, after step 202, the method further includes:
and displaying a first page at the display position of the target page, wherein the first page comprises a display page preset according to the content or type of the target page.
When the target page is abnormal, a blank state is usually presented, and in order to improve user experience, a first page can be displayed at a display position of the target page, wherein the first page is a display page preset according to the content or type of the target page, and the user experience is improved.
In this embodiment, in the development stage, some display interfaces may be preset according to the content and type of the target page. Specifically, the first page may include a preset display page according to the content of the target page, for example, the content of the target page that is mainly presented is related to food, the preset display page may be a food picture wall or the like, and when the target page is abnormal, the food picture wall is displayed; or, the first page may include a preset presentation page according to a type of the target page, for example, the type of the target page is a search page, and the preset presentation page may be a search front page or a search history page of the current search engine, and when an abnormality occurs in the search result, the search front page or the search history page of the search engine is displayed. It should be understood that the preset display interface is not limited thereto, and is not limited thereto.
It should be noted that the technical solution in this embodiment is also applicable to the embodiment shown in fig. 1, and has the same beneficial effects.
In this embodiment, when an abnormality occurs in a component of a target page, a target abnormality is captured in the component in which the abnormality occurs; packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information; and sending the target abnormal information to a background server. By packaging the component information into the anomaly information, a developer can determine the specific component with the anomaly through the component information without analyzing and processing each captured anomaly, so that the efficiency of locating the component-level source of the anomaly is improved, and the analysis time and cost are saved.
Referring to fig. 3, fig. 3 is a block diagram of an exception handling apparatus according to an embodiment of the present invention.
As shown in fig. 3, the exception handling apparatus 300 includes:
a capturing module 301, configured to capture, when an abnormality occurs in a component of the target page, a target abnormality in the component in which the abnormality occurs;
the injection module 302 is configured to encapsulate the component information of the component with the abnormality into the abnormality information of the target abnormality, and generate target abnormality information;
and the sending module 303 is configured to send the target exception information to a background server.
Optionally, the capturing module 301 is specifically configured to:
when an abnormality occurs in a first component of a target page, calling an abnormality capturing function to capture the target abnormality in the first component according to a preset abnormality capturing mechanism, wherein the first component is any component in the target page.
Optionally, as shown in fig. 4, the injection module 302 includes:
a generating unit 3021, configured to process the target abnormality, and generate first abnormality information, where the first abnormality information includes content and type of the target abnormality;
an obtaining unit 3022, configured to obtain component information of the first component, where the component information of the first component includes a component identifier, a component name, and a component position of the first component;
an injection unit 3023 for encapsulating the component information of the first component in the first abnormality information and generating target abnormality information.
Optionally, as shown in fig. 5, the apparatus 300 further includes:
the display module 304 is configured to display a first page at a display position of the target page, where the first page includes a display page preset according to content or type of the target page.
Referring to fig. 6, fig. 6 is a block diagram of an electronic device according to an embodiment of the present invention.
As shown in fig. 6, the electronic device 600 includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, wherein the processor 601, the communication interface 602, and the memory 603 perform communication with each other through the communication bus 604.
The memory 603 is used for storing a computer program.
The processor 601 is configured to execute a program stored in the memory 603, and implement the following steps:
when the component of the target page is abnormal, capturing target abnormality in the abnormal component;
packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information;
and sending the target abnormal information to a background server.
Optionally, when the component of the target page is abnormal, capturing the target abnormality in the abnormal component, including:
when an abnormality occurs in a first component of a target page, capturing the target abnormality in the first component according to a preset abnormality capturing mechanism, wherein the first component is any component in the target page.
Optionally, the encapsulating the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information includes:
processing the target abnormality to generate first abnormality information, wherein the first abnormality information comprises the content and the type of the target abnormality;
acquiring pre-stored component information of the first component, wherein the component information of the first component comprises a component identifier, a component name and a component position of the first component;
and packaging the component information of the first component in the first abnormal information to generate target abnormal information.
Optionally, after capturing the target exception in the abnormal component when the component of the target page is abnormal, the method further includes:
and displaying a first page at the display position of the target page, wherein the first page comprises a display page preset according to the content or type of the target page.
The communication bus 604 mentioned above for the electronic device 600 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, or the like. The communication bus 604 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
The communication interface 602 is used for communication between the electronic device 600 and other devices described above.
The memory 603 may include random access memory (Random Access Memory, simply RAM) or may include non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.
The processor 601 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
In yet another embodiment of the present invention, a computer readable storage medium is provided, in which instructions are stored, which when run on a computer, cause the computer to perform the exception handling method according to any of the above embodiments.
In yet another embodiment of the present invention, a computer program product containing instructions that, when run on a computer, cause the computer to perform the exception handling method of any of the above embodiments is also provided.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.
Claims (8)
1. An exception handling method, comprising:
when the component of the target page is abnormal, capturing target abnormality in the abnormal component;
packaging the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information, wherein the component information comprises identification information related to the component;
the target abnormal information is sent to a background server;
the step of encapsulating the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information includes:
processing the target abnormality to generate first abnormality information, wherein the first abnormality information comprises the content and the type of the target abnormality;
acquiring component information of a first component, wherein the component information of the first component comprises a component identifier, a component name and a component position of the first component; the first component is any component in the target page;
packaging the component information of the first component in the first abnormal information to generate target abnormal information;
when the component of the target page is abnormal, capturing the target abnormality in the abnormal component, wherein the method comprises the following steps:
when the first component of the target page is abnormal, capturing target abnormality in the first component according to a preset abnormality capturing mechanism, wherein due to the preset abnormality capturing mechanism, the abnormality occurring in the first component is captured by the first component.
2. The method of claim 1, wherein after capturing the target exception in the exception-occurring component when the exception occurs in the target page component, the method further comprises:
and displaying a first page at the display position of the target page, wherein the first page comprises a display page preset according to the content or type of the target page.
3. An exception handling apparatus for performing the exception handling method according to any one of claims 1-2, comprising:
the capturing module is used for capturing target abnormality in the abnormal component when the abnormal component of the target page occurs;
the injection module is used for encapsulating the component information of the component with the abnormality into the abnormality information of the target abnormality to generate target abnormality information;
and the sending module is used for sending the target abnormal information to a background server.
4. A device according to claim 3, characterized in that the capturing module is specifically configured to:
when an abnormality occurs in a first component of a target page, capturing the target abnormality in the first component according to a preset abnormality capturing mechanism, wherein the first component is any component in the target page.
5. The apparatus of claim 4, wherein the injection module comprises:
the generation unit is used for processing the target abnormality and generating first abnormality information, wherein the first abnormality information comprises the content and the type of the target abnormality;
the device comprises an acquisition unit, a storage unit and a storage unit, wherein the acquisition unit is used for acquiring the component information of the first component, and the component information of the first component comprises a component identifier, a component name and a component position of the first component;
and the injection unit is used for encapsulating the component information of the first component in the first abnormal information and generating target abnormal information.
6. A device according to claim 3, characterized in that the device further comprises:
the display module is used for displaying a first page at the display position of the target page, wherein the first page comprises a display page preset according to the content or type of the target page.
7. The electronic equipment is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 1-2 when executing a program stored on a memory.
8. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911201822.5A CN111026575B (en) | 2019-11-29 | 2019-11-29 | Abnormality processing method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911201822.5A CN111026575B (en) | 2019-11-29 | 2019-11-29 | Abnormality processing method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111026575A CN111026575A (en) | 2020-04-17 |
| CN111026575B true CN111026575B (en) | 2024-04-02 |
Family
ID=70203520
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911201822.5A Active CN111026575B (en) | 2019-11-29 | 2019-11-29 | Abnormality processing method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111026575B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978529A (en) * | 2015-03-10 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Exception handling method, exception handling system and exception handling server for webpage front end |
| CN106201811A (en) * | 2016-07-06 | 2016-12-07 | 青岛海信宽带多媒体技术有限公司 | The fault recovery method of application program and terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11188449B2 (en) * | 2016-05-31 | 2021-11-30 | Red Hat, Inc. | Automated exception resolution during a software development session based on previous exception encounters |
-
2019
- 2019-11-29 CN CN201911201822.5A patent/CN111026575B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104978529A (en) * | 2015-03-10 | 2015-10-14 | 腾讯科技（深圳）有限公司 | Exception handling method, exception handling system and exception handling server for webpage front end |
| CN106201811A (en) * | 2016-07-06 | 2016-12-07 | 青岛海信宽带多媒体技术有限公司 | The fault recovery method of application program and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111026575A (en) | 2020-04-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107908541B (en) | Interface testing method and device, computer equipment and storage medium | |
| CN110287696B (en) | Detection method, device and equipment for rebound shell process | |
| CN106708704B (en) | Method and device for classifying crash logs | |
| CN111782526A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN113114680B (en) | Detection method and detection device for file uploading vulnerability | |
| CN110647471A (en) | Interface test case generation method, electronic device and storage medium | |
| CN116595542B (en) | Vulnerability scanning method and system | |
| CN109657475A (en) | Code vulnerabilities check method, apparatus, equipment and storage medium | |
| CN114491560A (en) | Vulnerability detection method and device, storage medium and electronic equipment | |
| CN111008017B (en) | Oclin-based pre-review method for files to be submitted and related components | |
| CN110287700B (en) | iOS application security analysis method and device | |
| CN115186274A (en) | IAST-based security test method and device | |
| CN116346456A (en) | Business logic vulnerability attack detection model training method and device | |
| CN111767213B (en) | Database check point testing method and device, electronic equipment and storage medium | |
| CN111026575B (en) | Abnormality processing method and device and electronic equipment | |
| CN108156048A (en) | It is a kind of to realize the method and apparatus that application crashes information is obtained in complex scene | |
| CN116738091A (en) | Page monitoring method and device, electronic equipment and storage medium | |
| Mostafa et al. | Netdroid: Summarizing network behavior of android apps for network code maintenance | |
| CN112446030B (en) | Method and device for detecting file uploading vulnerability of webpage end | |
| CN114676436A (en) | Android application multimedia analysis library vulnerability mining system and method based on structural variation | |
| CN109189369B (en) | Method and device for compressing codes | |
| CN113778800A (en) | Error reporting information processing method, device, system, equipment and storage medium | |
| CN113535580A (en) | CTS (clear to send) testing method, device and testing equipment | |
| US11816022B2 (en) | Snapshot simulation of service module responses | |
| CN113238953A (en) | UI automation test method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |