WO2017124808A1

WO2017124808A1 - Fault information reproduction method and reproduction apparatus

Info

Publication number: WO2017124808A1
Application number: PCT/CN2016/103891
Authority: WO
Inventors: 沈中平
Original assignee: 上海斐讯数据通信技术有限公司
Priority date: 2016-01-20
Filing date: 2016-10-29
Publication date: 2017-07-27
Also published as: CN105718354A

Abstract

A fault information reproduction method and reproduction apparatus, used for reproducing a fault so as to solve the fault. The reproduction method comprises: the step of determining a fault log of a client (S101); the step of determining fault data associated with the fault log according to the fault log (S102); the step of acquiring the fault log and the fault data (S103); and the step of debugging the fault log and the fault data so as to reproduce fault information about the client (S104). It is convenient to debug by means of a fault log and fault data, hence, the reproduction of a fault of a client is facilitated, thereby facilitating the analysis and repair of this fault.

Description

Method for reproducing fault information and reproducing device

Technical field

The present invention relates to the field of mobile devices, and in particular, to a method and a reproducing apparatus for reproducing fault information.

Background technique

In recent years, many Android-based smartphones have appeared on the market. After being released to the market, these mobile phones are often reflected by customers in the process of flashback, black screen, crashes and the like. These faults are often not reproducible, and only the one used by the user has that phenomenon.

R&D personnel often cannot reproduce this fault phenomenon after receiving the report. In the prior art, it is necessary to collect the information causing the fault in the user's mobile phone for analysis, in order to avoid or improve the problem in the new version of the software. Specifically, the fault log of the mobile device in a certain period of time is collected through the field indicating the fault in the log, and sent to the server that collects the fault.

However, in today's increasingly complex software systems, large-capacity data is often loaded and processed. Since it is not easy to print out the fault logs that may cause failures, the R&D personnel cannot accurately locate the problems from only part of the fault logs. .

Summary of the invention

It is an object of the present invention to provide a method and a reproducing apparatus for reproducing fault information for reproducing a fault to solve the fault problem.

According to an aspect of the present invention, a method for reproducing fault information is provided, wherein the method comprises the following steps:

Determine the fault log of the client;

Determining fault data associated with the fault log according to the fault log;

Obtaining the fault log and fault data;

The fault log and the fault data are debugged to reproduce the fault information of the client.

Preferably, the method for determining a fault log of a client includes:

Scan the client running log for fault keywords that indicate errors. If yes, determine the fault log corresponding to the faulty keyword that indicates the fault within a preset period of time.

Preferably, the method for determining fault data associated with the fault log according to the fault log comprises:

The fault data associated therewith is determined according to the path recorded in the fault log. The path of the installation fault log of the present invention determines the fault data that is expected to be associated with each other, and the operation steps in the user mobile device during the fault process are acquired during the debugging process.

Preferably, the method for obtaining the fault log and fault data includes:

Obtain a packaged compressed file that is packaged and compressed by the fault log and the fault data.

Preferably, the method for debugging the fault log and the fault data to reproduce the fault information of the client includes:

The content of the client operation step is extracted in the fault log. The process of reversing the user's mobile device is reproduced when the specific content of the operation steps of the client at the time of the failure is extracted.

Preferably, after the fault log and the fault data are debugged to reproduce the fault information of the client, the method further includes:

The fault information is repaired by the fault log and the fault data, and repair information is generated. After the failed fault log and fault data are repaired, the root cause of the fault is resolved, preventing such faults from occurring in later versions.

Preferably, detecting whether the repair information reproduces the fault information,

If the fault information is reproduced, the fault information is repaired again until the fault information is not reproduced;

If the fault information is not reproduced, it is confirmed that the fault information is repaired. The invention further tests the repaired information content to ensure that such fault information has been repaired.

According to another aspect of the present invention, there is also provided a reproducing apparatus for fault information, wherein the reproducing apparatus comprises the following:

Means for determining a fault log of the client;

Means for determining fault data associated with the fault log based on the fault log;

Means for obtaining the fault log and fault data;

Means for debugging the fault log and fault data to reproduce fault information of the client.

Preferably, the means for determining the fault log of the client is configured to:

Preferably, the means for determining fault data associated with the fault log based on the fault log is configured to:

The fault data associated therewith is determined according to the path recorded in the fault log.

Preferably, the means for obtaining the fault log and fault data is configured to:

Preferably, the means for debugging the fault log and fault data to reproduce the fault information of the client is configured to:

The content of the client operation step is extracted in the fault log.

Preferably, the reproducing apparatus further comprises means for repairing the fault information and generating fault information through the fault log and fault data.

Preferably, the reproducing apparatus further comprises means for detecting whether the repair information reproduces the fault information;

If the fault information is detected to be reproduced, the fault information is repaired again until the fault information is not reproduced;

If it is detected that the fault information is not reproduced, it is confirmed that the fault information is repaired.

During the use of the mobile device, fault information may occur, such as: flashback, black screen, crash, etc.; in the prior art, when the fault information is solved, the fault information is generally acquired first. The mobile device causes the faulty information to be analyzed so that such a fault no longer occurs in a later new version of the mobile device. The specific solution is to collect the fault log in a period of time in the mobile device running log to identify the fault, send the fault log to the server, and reproduce the fault information according to the fault log, and the fault information is conveniently analyzed. The specific cause of the failure, and it is convenient to repair this fault. However, it is difficult to reproduce the fault information only by relying on the fault log analysis, and thus it is impossible to fix the fault, so that the new version of the mobile device cannot be improved in the later stage.

Compared with the prior art, the present invention has the following advantages: the present invention first determines a fault log of a client, and determines fault data associated with the fault log according to the fault log, that is, determines a fault in the user mobile device running log. The fault log of the field and the fault data associated with the fault log; the server side acquires the fault log and the fault data at the same time, and debugs the fault log and the fault data to reproduce the fault information of the client. Since the invention extracts the fault data associated with the fault information before acquiring the fault log, the combination of the fault log and the fault data facilitates debugging, and thus the fault information of the client is easily reproduced, that is, the user is easily re-appeared by debugging. The failure of the mobile device; in turn, it is convenient to analyze the fault information that is faulty, so as to repair the fault information and prevent such faults from occurring in the new version of the mobile device.

DRAWINGS

Other features, objects, and advantages of the present invention will become more apparent from the Detailed Description of Description

1 is a schematic flow chart of a method for reproducing fault information according to an embodiment of the present invention;

2 is a schematic flowchart of a method for reproducing fault information according to another embodiment of the present invention;

3 is a schematic structural diagram of a device for reproducing fault information according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a device for reproducing fault information according to another embodiment of the present invention.

The same or similar reference numerals in the drawings denote the same or similar components.

detailed description

Before discussing the exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as a process or method depicted as a flowchart. Although the flowcharts describe various operations as a sequential process, many of the operations can be implemented in parallel, concurrently or concurrently. In addition, the order of operations can be rearranged. The process may be terminated when its operation is completed, but may also have additional steps not included in the figures. The processing may correspond to methods, functions, procedures, subroutines, subroutines, and the like.

By "computer device", also referred to as "computer" in the context, is meant an intelligent electronic device that can perform predetermined processing, such as numerical calculations and/or logical calculations, by running a predetermined program or instruction, which can include a processor and The memory is executed by the processor to execute a predetermined process pre-stored in the memory to execute a predetermined process, or is executed by hardware such as an ASIC, an FPGA, a DSP, or the like, or a combination of the two. Computer devices include, but are not limited to, servers, personal computers, notebook computers, tablets, smart phones, and the like.

The computer device includes a user device and a network device. The user equipment includes, but is not limited to, a computer, a smart phone, a PDA, etc.; the network device includes but is not limited to a single network server, a server group composed of multiple network servers, or a cloud computing based computer Or a cloud composed of a network server, wherein cloud computing is a type of distributed computing, a super virtual computer composed of a group of loosely coupled computers. Wherein, the computer device can be operated separately to implement the present invention, and can also access the network and implement the present invention by interacting with other computer devices in the network. The network in which the computer device is located includes, but is not limited to, the Internet, a wide area network, a metropolitan area network, a local area network, a VPN network, and the like.

It should be noted that the user equipment, the network equipment, the network, and the like are merely examples, and other existing or future possible computer equipment or networks, such as those applicable to the present invention, are also included in the scope of the present invention. It is included here by reference.

The methods discussed below, some of which are illustrated by flowcharts, can be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. The process used to perform the necessary tasks when implemented in software, firmware, middleware, or microcode. The serial code or code segments can be stored in a machine or computer readable medium such as a storage medium. The processor(s) can perform the necessary tasks.

The specific structural and functional details disclosed are merely representative and are for the purpose of describing exemplary embodiments of the invention. The present invention may, however, be embodied in many alternative forms and should not be construed as being limited only to the embodiments set forth herein.

It should be understood that although the terms "first," "second," etc. may be used herein to describe the various elements, these elements should not be limited by these terms. These terms are used only to distinguish one unit from another. For example, a first unit could be termed a second unit, and similarly a second unit could be termed a first unit, without departing from the scope of the exemplary embodiments. The term "and/or" used herein includes any and all combinations of one or more of the associated listed items.

It will be understood that when a unit is referred to as "connected" or "coupled" to another unit, it can be directly connected or coupled to the other unit, or an intermediate unit can be present. In contrast, when a unit is referred to as being "directly connected" or "directly coupled" to another unit, there is no intermediate unit. Other words used to describe the relationship between the units should be interpreted in a similar manner (eg "between" and "directly between" and "adjacent to" Than "directly adjacent to", etc.).

The terminology used herein is for the purpose of describing the particular embodiments, The singular forms "a", "an", It is also to be understood that the terms "comprising" and """ Other features, integers, steps, operations, units, components, and/or combinations thereof.

It should also be noted that, in some alternative implementations, the functions/acts noted may occur in a different order than that illustrated in the drawings. For example, two figures shown in succession may in fact be executed substantially concurrently or sometimes in the reverse order, depending on the function/acts involved.

The invention is further described in detail below with reference to the accompanying drawings.

FIG. 1 is a schematic flowchart diagram of a method for reproducing fault information according to an embodiment of the present invention. FIG. 3 is a schematic structural diagram of a device for reproducing fault information according to an embodiment of the present invention. The method of reproducing the failure information includes step S101, step S102, step S103, and step S104 performed by the reproducing apparatus in FIG.

The method for reproducing fault information in this embodiment is mainly implemented by a network device and a user equipment debugger; the user equipment debugger includes but is not limited to a PC, a tablet, a smart phone, a PDA, etc.; the network device Including but not limited to a single network server, a server group composed of multiple network servers, or a cloud computing-based cloud composed of a large number of computers or network servers, wherein cloud computing is a kind of distributed computing, consisting of a group of loose A super virtual computer consisting of a set of coupled computers. The debugger in this embodiment is described by taking a mobile phone as an example, and the network device is described by taking a server as an example.

It should be noted that the user equipment mobile phone is only an example, and other existing or future network devices and user equipment may be applicable to the present invention, and are also included in the scope of the present invention and are included by reference. herein.

The method according to the present embodiment includes step S101, step S102, step S103, and step S104.

In step S101, the reproducing apparatus first determines the failure log of the client.

The replay device runs in the background of the user's client and automatically collects the fault log. The client in this embodiment is described by taking a user's mobile phone as an example.

Specifically, the replay device automatically scans the running log of the user client, and when a field indicating the error (for example, Fatal Exception) appears in the running log of the scan, the log in the preset time period is automatically collected, and is defined as a fault log. Error.log); and store this fault log in a file.

It should be noted that the above examples are only for better explaining the technical solutions of the present invention, and are not intended to limit the present invention. Those skilled in the art should understand that any method for determining the fault log by the client should be included in the scope of the present invention. Inside.

In step S102, the reproducing device determines the fault date according to the fault log. The fault data associated with the Zhi.

After the replay device automatically collects the fault log, the data associated with the fault is collected according to the content in the fault log, and is defined as fault data herein;

Specifically, the automatically collected log in the preset time period may be: obtaining the last loaded interface name from the running log (for example: Compose Message Activity). The user operation information is further printed, and the fault data includes the user operation information, and the fault data includes information of the user operation during the fault occurrence, so that the fault is easily reproduced by the debugger.

In addition, the fault data may further include path information recorded in the fault log. It should be noted that the fault data of this embodiment is not limited to the path information and the user operation information, and may also include other information associated with the fault log. Of course, the fault data of this embodiment may also include user operation information alone or separately include path information.

In step S103, the reproducing device acquires the fault log and fault data;

After the reproducing device determines the fault log and the fault data, the fault log and the fault data are sent to the server.

Specifically, the fault log and the fault data are packaged into a folder, compressed, and the compressed folder is sent to the server, and the compressed folder is sent to the server when the network is unblocked. It should be noted that this is only a specific example of obtaining the fault log and the fault data by the reproducing device. The embodiment is not limited thereto, and other methods may be obtained, such as: not compressing and packaging, directly confirming The fault log and fault data are sent to the server.

In step S104, the reproducing device debugs the fault log and the fault data to reproduce the fault information of the client.

The content of the operation step of the client is reflected in the fault log.

Specifically, after obtaining the packaged compressed folder from the server, extract the compressed folder, and open the files to obtain the fault log and the fault data, and put the fault log and the fault data into the processing software related directory on the PC. And connecting the debugging mobile phone to the PC, the processing software automatically imports the user data into the corresponding directory in the debugging mobile phone connected to the PC according to the path recorded in the collected data file description (Collect.log); And extract and display the contents of the user operation steps reflected in the fault log (error.log). This makes it possible to reproduce this fault, which in turn facilitates analysis and finds the cause of the fault, so that the program can be modified in the later process, and the new apk can be imported into the mobile phone to prevent such a fault from occurring in the new version of the mobile phone.

The mobile device will have fault information during use, such as flashback, black screen, crash and the like.

In the prior art, when the fault information is solved, the information caused by the fault of the user mobile device is generally first analyzed, so that such a fault does not occur in the new version of the mobile device. The specific solution is to collect the fault log in a period of time in the mobile device running log to identify the fault, send the fault log to the server, and reproduce the fault information according to the fault log, and the fault information is conveniently analyzed. The specific cause of the failure, and it is convenient to repair this fault. However, it is difficult to reproduce the fault information only by relying on the fault log analysis, and thus it is impossible to fix the fault, so that the new version of the mobile device cannot be improved in the later stage.

In this embodiment, the fault log of the client is first determined, and the fault data associated with the fault log is determined according to the fault log, that is, the fault log of the field indicating the fault in the user mobile device running log is determined and related to the fault log. The fault data of the joint; the server side obtains the fault log and the fault data at the same time, and debugs the fault log and the fault data to reproduce the fault information of the client. Because the fault data associated with the fault information is extracted before the fault log is obtained, the combination of the fault log and the fault data facilitates debugging, and thus the fault information of the client is easily reproduced, that is, it is easy to reappear through debugging. The failure of the user's mobile device; in turn, it is convenient to analyze the faulty fault information in order to repair the fault information and prevent such faults from occurring in the new version of the mobile device.

It should be noted that the above examples are only for better explaining the technical solutions of the present invention, and are not limited to the present invention. Those skilled in the art should understand that any of the fault data obtained by acquiring the fault log and the fault log is reproduced. The method of fault information should be included in the scope of the present invention.

FIG. 2 is a schematic flowchart diagram of a method for reproducing fault information according to another embodiment of the present invention. The method of the present embodiment is mainly implemented by a reproducing apparatus, wherein any description of the reproducing apparatus in the embodiment shown in Fig. 1 is incorporated herein by reference.

The method according to the present embodiment includes step S201, step S202, step S203, step 204, step 205, and step 206.

The step S201 can refer to step S101 in FIG. 1 , step S202 can refer to step S102 in FIG. 1 , step S203 can refer to step S103 in FIG. 1 , and step S204 can refer to step S104 in FIG. 1 . The embodiment in 1 has been described in detail and will not be described herein.

That is, the embodiment shown in FIG. 2 differs from that in FIG. 1 in that the embodiment shown in FIG. 2 further includes step S205 and step S206.

In step S205, after the fault log and the fault data are debugged to reproduce the fault information of the client, the method further includes:

The fault information is repaired by the fault log and the fault data, and repair information is generated.

Among them, by recreating this fault, analyzing and finding the cause of the fault, and then modifying the program to import the new apk into the mobile phone, thereby realizing the repair of the fault.

In step S206, detecting whether the repair information reproduces the fault information,

If the fault information is not reproduced, it is confirmed that the fault information is repaired.

That is, when it is detected that the repair information does not reproduce the fault information, it is confirmed that the fault information is repaired;

When the repair information is detected to reproduce the fault information, the fault information is repaired again until the fault information is not reproduced.

That is, in this embodiment, the repaired information is further checked and confirmed. If the fault information that has occurred is reproduced, the process returns to step S205 to continue repairing the fault information, and another new repair information is generated. Until the information to ensure that the repair is complete does not reproduce the fault. Make sure that the repaired information no longer has this type of failure.

It should be noted that the above examples are only for better explaining the technical solutions of the present invention, and are not limited to the present invention. Those skilled in the art should understand that any client user's letter repairs the recurring faults and repairs The method of detecting the subsequent information should be included in the scope of the present invention.

FIG. 3 is a schematic structural diagram of a device for reproducing fault information according to an embodiment of the present invention. The apparatus for reproducing fault information (hereinafter referred to as "reproducing apparatus") includes means for determining a fault log of the client (hereinafter referred to as "first fault log determining means 301") for determining according to the fault log a device for fault data associated with the fault log (hereinafter referred to as "first fault data confirming device 302"), a device for acquiring the fault log and fault data (hereinafter referred to as "first acquiring device 303"), And means for debugging the fault log and the fault data to reproduce the fault information of the client (hereinafter referred to as "the first debug device 304").

The first fault log confirming device 301 is configured to confirm the fault log of the client user.

The first fault log confirming device 301 runs in the background of the user's client and automatically collects the fault log. The client in this embodiment is described by taking a user's mobile phone as an example.

Specifically, the first fault log confirming device 301 automatically scans the running log of the user client, and automatically collects the log in the preset time period when a field indicating the error (for example, Fatal Exception) appears in the running log of the scan, and is defined herein. Is the fault log (error.log); and stores this fault log in a file.

It should be noted that the above examples are only for better explaining the technical solutions of the present invention, and are not intended to limit the present invention. Those skilled in the art should understand that any device for determining the fault log by the client should be included in the scope of the present invention. Inside.

The first failure data confirming means 302 determines the fault data associated with the fault log based on the fault log.

After the first fault log confirming device 301 automatically collects the fault log, the data associated with the fault is collected according to the content in the fault log, and is defined as fault data herein;

Specifically, the automatically collected log in the preset time period may be: from the running log. Get the last loaded interface name (for example: Compose Message Activity). The user operation information is further printed, and the fault data includes the user operation information, and the fault data includes information of the user operation during the fault occurrence, so that the fault is easily reproduced by the debugger.

The first obtaining means 303 acquires the fault log and fault data.

After the first fault log confirming device and the first fault data confirming device respectively determine the fault log and the fault data, the fault log and the fault data are sent to the server.

Specifically, the fault log and the fault data are packaged into a folder, compressed, and the compressed folder is sent to the server, and the compressed folder is sent to the server when the network is unblocked. It should be noted that this is only a specific example of obtaining the fault log and the fault data by the first acquiring device. The embodiment is not limited thereto, and other obtaining manners may be used, for example, the compression and packaging are not performed, and the confirmation is directly performed. The fault log and fault data are sent to the server.

The first debugging device 304 debugs the fault log and the fault data to reproduce the fault information of the client.

The content of the operation step of the client is reflected in the fault log.

Specifically, after obtaining the packaged compressed folder from the server, extract the compressed folder, and open the files to obtain the fault log and the fault data, and put the fault log and the fault data into the processing software related directory on the PC. And connecting the debugging mobile phone to the PC, the processing software automatically imports the user data into the corresponding directory in the debugging mobile phone connected to the PC according to the path recorded in the collected data file description (Collect.log); and the fault log ( The content of the user operation steps reflected in error.log) is extracted and displayed. This makes it possible to reproduce this fault, which in turn facilitates analysis and finds the cause of the fault, so that the program can be modified in the later process, and the new apk can be imported into the mobile phone to prevent such a fault from occurring in the new version of the mobile phone.

In this embodiment, the fault log of the client is first determined, and the fault data associated with the fault log is determined according to the fault log, that is, the fault log of the field indicating the fault in the user mobile device running log is determined and related to the fault log. The fault data of the joint; the server side obtains the fault log and the fault data at the same time, and debugs the fault log and the fault data to reproduce the fault information of the client. Since the embodiment extracts the fault data associated with the fault information before acquiring the fault log, the combination of the fault log and the fault data facilitates debugging, and thus the fault information of the client is easily reproduced, that is, the user is easily re-appeared by debugging. The failure of the mobile device; in turn, it is convenient to analyze the fault information that is faulty, so as to repair the fault information and prevent such faults from occurring in the new version of the mobile device.

It should be noted that the above examples are only for better explaining the technical solutions of the present invention, and are not limited to the present invention. Those skilled in the art should understand that any of the fault data obtained by acquiring the fault log and the fault log is reproduced. The means for fault information should be included in the scope of the present invention.

4 is a schematic structural diagram of a replaying push device for fault information according to another embodiment of the present invention. In conjunction with FIG. 3, the device for reproducing fault information (hereinafter referred to as "reproducing device") includes a fault for determining a client. a device for logging (hereinafter referred to as "second failure log determining device 401") for determining association with the failure log according to the failure log Device for fault data (hereinafter referred to as "second fault data confirming device 402"), means for acquiring the fault log and fault data (hereinafter referred to as "second acquiring device 403"), for using the fault log And means for debugging the fault data to reproduce the fault information of the client (hereinafter referred to as "second debug device 404"), means for repairing the fault information by the fault log and fault data, and generating repair information ( Hereinafter, the "repair device 405"), and means for detecting whether the repair information reproduces the fault information (hereinafter referred to as "detection device 406") means for pushing the recurring fault information (hereinafter referred to as " The push device "reproducing device" includes means for acquiring user information of the client (hereinafter referred to as "second obtaining device 401"), and is configured to determine, according to the user information of the client, a to-be-sent that matches the user information. a device for information (hereinafter referred to as "second determining device 402"), an application entry control area for pushing the information to be sent to an application of the client A device for displaying a line (hereinafter referred to as "second transmitting device 403") and a device for establishing a personal information file based on registration information and usage information of the application (hereinafter referred to as "first personal information device 404").

The second fault log determining device 401 can refer to the first fault log determining device 301 in FIG. 3, and the second fault data confirming device 402 can refer to the first fault data confirming device 302 in FIG. 3, and the second acquiring device. 403 can refer to the first obtaining device 303 in FIG. 3, and the second debugging device 404 can refer to the first debugging device 304 in FIG. 3. The embodiment in FIG. 3 has been described in detail, and details are not described herein again.

That is, the embodiment shown in FIG. 4 differs from that in FIG. 3 in that the embodiment shown in FIG. 4 further includes a repairing device and a detecting device.

The repairing device repairs the fault information through the fault log and the fault data, and generates repair information.

Repairing the device, detecting whether the repair information reproduces the fault information,

In this case, the present embodiment further confirms the repaired information, and if the fault information appears, the fault information is further repaired, and another new repair information is generated until the detection and repair is ensured. The completed information no longer reproduces the fault. Make sure that the repaired information no longer has this type of failure.

It should be noted that the above examples are only for better explaining the technical solutions of the present invention, and are not limited to the present invention. Those skilled in the art should understand that any client user's letter repairs the recurring faults and repairs. The means for detecting the subsequent information should be included in the scope of the present invention.

In addition, the reproducing apparatus of this embodiment may not include the detecting device, and may be repaired only by the repairing device.

In the present invention, the reproducing apparatus may include a log mobile phone module, a process retrieval module, and a data storage module. The log collection module collects the log of the mobile phone running and stores it in a file, and the content of the scan log is incorrectly represented by Fatal Exception. In the field, the last loaded interface name (such as ComposeMessageActivity) and some user operation information printed afterwards are obtained from the log, and the content is passed to the process retrieval module. The process retrieval module may include a database for recording the process (Process) of the client running log, the current interface name (ScreenName), and the data file (CollectFile) and the data path (CollectDir) stored in the mobile phone involved in the interface. Some interfaces need to collect more data for certain operations. There are additional fields to store the operations involved in the log. This information is used to determine the data to be packaged and passed to the data storage module.

For example: the table records in this database are shown in Table 1 below:

Table 1

The reproducing device may further comprise a data collecting module and a data sending module:

Find the file path and folder to be collected from the process retrieval module, and then generate a collection file description file Collect.log, and then package these files and the fault log information into a folder, when Sent to the server when the network is unblocked.

The Collect.log file format can be:

Target directory local directory

Data/data/com.providers.contacts/databases database

Data/data/com.providers.contacts/files files

The purpose is to enable the PC-side software to read and import the collected files into the corresponding directory (target directory) of the debug phone.

Let's take a crash log of the collected SMS module as an example to illustrate the search. process:

The log collection module scans the faulty keyword FATAL EXCEPTION, and then searches up the last load interface keyword Load screen and process Process, finds the last loaded interface name as ComposeMessageActivity, and the process name is com.android.mms, finds the data table. The record with the id of 1 corresponds to the data/data/com.providers.telephony/mmssms.db file and the path data/data/com.providers.telephony/app_parts to be collected according to the requirements of this record. The data collection module and the data sending module, the data collection module and the data sending module copy the files and folders in the user's mobile phone, generate a Collect.log file, and write the path of the collected files and folders, and then The log file is intercepted for a certain period of time as the fault log error.log. These files are packaged and compressed and sent to the server. After obtaining the fault file package from the server, the R&D personnel put it in the corresponding directory of the PC software of the system. The PC software first imports the mmssms.db file and the app_parts folder into the debug phone according to the contents recorded in the Collect.log. In the directory, then read the contents of error.log, display the contents of the filtered user operation on the interface, and the developer enters according to the displayed operation steps (observation keyword Load Screen, Operation). The ComposeMessageActivity interface is operated on this interface according to the Operation content displayed by the PC software, in order to reproduce the user's fault. After recurring the fault, try to analyze how to modify the program. After the modification, import the new apk and verify the modification result on this debugging machine.

It should be noted that the present invention can be implemented in software and/or a combination of software and hardware. For example, the various devices of the present invention can be implemented using an application specific integrated circuit (ASIC) or any other similar hardware device. In one embodiment, the software program of the present invention may be executed by a processor to implement the steps or functions described above. Likewise, the software program (including related data structures) of the present invention can be stored in a computer readable recording medium such as a RAM memory, a magnetic or optical drive or a floppy disk and the like. Additionally, some of the steps or functions of the present invention may be implemented in hardware, for example, as a circuit that cooperates with a processor to perform various steps or functions.

It is apparent to those skilled in the art that the present invention is not limited to the details of the above-described exemplary embodiments, and the present invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the present embodiments are to be considered as illustrative and not restrictive, and the scope of the invention is defined by the appended claims instead All changes in the meaning and scope of equivalent elements are included in the present invention. Any reference signs in the claims should not be construed as limiting the claim. In addition, it is to be understood that the word "comprising" does not exclude other elements or steps. A plurality of units or devices recited in the system claims can also be implemented by a unit or device by software or hardware. The first, second, etc. words are used to denote names and do not denote any particular order.

While the invention has been shown and described with reference to the embodiments of the embodiments of the invention The protection sought herein is set forth in the appended claims. These and other aspects of various embodiments are set forth in the following numbering clauses:

Claims

A method for reproducing fault information, characterized in that the method for reproducing comprises the following steps:

Determine the fault log of the client;

Determining fault data associated with the fault log according to the fault log;

Obtaining the fault log and fault data;

The fault log and the fault data are debugged to reproduce the fault information of the client.
The method for reproducing fault information according to claim 1, wherein the method for determining a fault log of the client comprises:

Scan the client running log for fault keywords that indicate errors. If yes, determine the fault log corresponding to the faulty keyword that indicates the fault within a preset period of time.
The method for reproducing fault information according to claim 1, wherein the method for determining fault data associated with the fault log according to the fault log comprises:

The fault data associated therewith is determined according to the path recorded in the fault log.
The method for reproducing a fault of a mobile phone according to claim 1, wherein the method for acquiring the fault log and the fault data comprises:

Obtain a packaged compressed file that is packaged and compressed by the fault log and the fault data.
The method for reproducing fault information according to claim 1, wherein the method for debugging the fault log and the fault data to reproduce the fault information of the client includes:

The content of the client operation step is extracted in the fault log.
The method for reproducing fault information according to claim 1, wherein after the fault log and the fault data are debugged to reproduce the fault information of the client, the method further includes:

The fault information is repaired by the fault log and the fault data, and repair information is generated.
A method for reproducing fault information according to claim 6, wherein the detecting station Whether the repair information reproduces the fault information,

If the fault information is reproduced, the fault information is repaired again until the fault information is not reproduced;

If the fault information is not reproduced, it is confirmed that the fault information is repaired.
A reproducing device for fault information, characterized in that the reproducing device comprises the following devices:

Means for determining a fault log of the client;

Means for determining fault data associated with the fault log based on the fault log;

Means for obtaining the fault log and fault data;

Means for debugging the fault log and fault data to reproduce fault information of the client.
The apparatus for reproducing fault information according to claim 8, wherein the means for determining the fault log of the client is configured to:

Scan the client running log for fault keywords that indicate errors. If yes, determine the fault log corresponding to the faulty keyword that indicates the fault within a preset period of time.
The apparatus for reproducing fault information according to claim 8, wherein the means for determining fault data associated with the fault log based on the fault log is configured to:

The fault data associated therewith is determined according to the path recorded in the fault log.
The apparatus for reproducing fault information according to claim 8, wherein the means for acquiring the fault log and the fault data is configured to:

Obtain a packaged compressed file that is packaged and compressed by the fault log and the fault data.
The apparatus for reproducing fault information according to claim 8, wherein the means for debugging the fault log and the fault data to reproduce the fault information of the client is configured to:

The content of the client operation step is extracted in the fault log.
A reproducing apparatus for fault information according to claim 8, wherein The reproducing apparatus further includes means for repairing the fault information and generating fault information by the fault log and fault data.
The apparatus for reproducing fault information according to claim 13, wherein said reproducing means further comprises means for detecting whether said repair information reproduces said fault information;

If the fault information is detected to be reproduced, the fault information is repaired again until the fault information is not reproduced;

If it is detected that the fault information is not reproduced, it is confirmed that the fault information is repaired.