WO2020173377A1

WO2020173377A1 - Log information generating method and apparatus, and electronic device

Info

Publication number: WO2020173377A1
Application number: PCT/CN2020/076020
Authority: WO
Inventors: 张烽; 张瑞荣; 李翠琴
Original assignee: 华为技术有限公司
Priority date: 2019-02-28
Filing date: 2020-02-20
Publication date: 2020-09-03
Also published as: CN111625431A; CN111625431B

Abstract

A log information generating method and apparatus, and an electronic device. The method comprises: an electronic device receiving a first operation of a user; and in response to the first operation, the electronic device generating a tracing identifier that uniquely corresponds to a service, and transmitting the tracing identifier in a whole calling link of the service (301); and the electronic device storing the tracing identifier in a calling record of each thread of each process of the calling link, and generating log information comprising the tracing identifier (302). The method facilitates a developer in screening, according to the tracing identifier of each service, log information related to the service, reduces the requirements for the capability of the developer, and improves the problem solving efficiency.

Description

A log information generation method, device and electronic equipment This application requires that it be submitted to the State Intellectual Property Office of China on February 28, 2019, the application number is 201910151968.7, and the invention title is "a log information generation method, device and electronic equipment" The priority of the Chinese patent application, the entire content of which is incorporated in this application by reference. Technical field

This application relates to the field of terminal technologies, and in particular, to a method, device, and electronic device for generating log information. Background technique

At present, in the development process of the Android operating system of the smartphone, the analysis and resolution of functional and performance problems depend on the information output by the log and the performance trace log (systrace). In the prior art, the flow log of the Android system outputs the information in business processing through the log system. For example, the log output format of the Android system includes timestamp, process ID, thread ID, level, and content. Some problems (such as slow taking pictures) in practical applications often involve multiple services and multiple levels of the Android system. Therefore, the log information includes different businesses, different processes, and different threads, so it is difficult to distinguish from a certain business. The relevant parts can only be distinguished manually. Since the Android system itself has multiple layers and is relatively complicated, a developer is generally only familiar with a certain business or a certain level of the business. Therefore, in order to troubleshoot problems, developers often need to manually filter useful information from a large amount of log information, that is, to extract the parts related to the business processing process of the problem, which requires a higher ability of the developer, and the method is more efficient in solving the problem. low. Summary of the invention

This application provides a method, device and electronic equipment for generating log information, which are used to generate log information including tracking identification, so that developers can screen information related to the business according to the tracking identification of each business, and reduce the ability requirements for developers , Improve problem solving efficiency.

In a first aspect, an embodiment of the present application provides a method for generating log information. The method is applicable to an electronic device. The method includes: the electronic device receives a user's first operation, and in response to the first operation, the electronic device enters the service startup portal Add a unique tracking identifier corresponding to the service, and transfer the tracking identifier in the entire call link of the service, and then the electronic device stores the tracking identifier in the call of each thread of each process of the call link In the recording, log information including the tracking identifier is generated. Wherein, the tracking identifier may be generated according to the identifier of the electronic device and the occurrence time of the first operation.

The embodiment of the application can realize that the calling link of a service carries a unique tracking identifier, so that developers can quickly locate the time-consuming thread by calling the log information corresponding to the tracking identifier, thereby Locate the cause of the fault.

In a possible design, the log information includes the call timestamp of the thread, the call service name, and the call relationship of other threads. The electronic device can also generate the call time stamp, the call service name, and the call relationship in the log information. Report that the call link is abnormal. In this way, the analysis process of the developer can be saved and the problem solving efficiency can be improved.

In a possible design, after the electronic device generates the unique tracking identifier corresponding to the service, it writes the tracking identifier into the context of the first thread corresponding to the service portal, and then uses the communication message to transfer the tracking identifier from the first thread. The thread is passed to the second thread, and the tracking identifier is written into the context of the second thread. If the second thread is not the most In the latter thread, the tracking identifier is transferred from the second thread to the third thread through the communication message, and the tracking identifier is written into the context of the third thread until the last thread of the call link is repeatedly executed. It can be seen that this method can realize the transfer of the tracking identifier in the call link.

In a possible design, the electronic device obtains the trace identifier from the context of each thread of the call link; and then writes the character string obtained by the conversion of the trace identifier into each process of the call link In the call record of each thread, finally generate log information including the tracking identifier. Wherein, the log includes at least one of a running log, a kernel log, and a performance tracking log.

In a second aspect, an embodiment of the present application provides an electronic device, including a processor and a memory. The memory is used to store one or more computer programs; when the one or more computer programs stored in the memory are executed by the processor, the electronic device can implement any one of the possible design methods in any of the foregoing aspects.

In a third aspect, an embodiment of the present application also provides a device, which includes a module/unit that executes any possible design method of any of the above aspects. These modules/units can be realized by hardware, or by hardware executing corresponding software.

In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium, where the computer-readable storage medium includes a computer program, and when the computer program runs on an electronic device, the electronic device executes any of the above aspects. Any one of the possible design methods.

In a fifth aspect, the embodiments of the present application also provide a method that includes a computer program product, which when the computer program product runs on a terminal, causes the electronic device to execute any one of the possible designs in any of the foregoing aspects.

These and other aspects of the present application will be more easily understood in the description of the following embodiments. Description of the drawings

Figure 1 is a schematic diagram of an existing log screening method provided by an embodiment of the application;

Figure 2 is a schematic diagram of an application scenario provided by an embodiment of the application;

FIG. 3 is a schematic structural diagram of a mobile phone provided by an embodiment of the application;

FIG. 4 is a schematic structural diagram of an Android operating system provided by an embodiment of the application;

FIG. 5 is a schematic structural diagram of an improved Android operating system provided by an embodiment of the application;

FIG. 6 is a schematic flowchart of a method for generating log information according to an embodiment of the application;

FIG. 7 is a schematic diagram of the tracking identification transfer of the binder communication mechanism provided by an embodiment of the application;

FIG. 8 is a schematic diagram of the tracking identification transfer of the handler communication mechanism provided by an embodiment of the application;

FIG. 9 is a schematic diagram of a tracking identification transfer interaction flow based on binder synchronization calls provided by an embodiment of the application; FIG. 10 is a schematic diagram of a log automatic screening method provided by an embodiment of the application;

Figure 11a and Figure lib are schematic diagrams of a fault location method for a performance tracking log provided in an embodiment of the application.

FIG. 12 is a schematic diagram of a device provided by an embodiment of this application;

FIG. 13 is a schematic structural diagram of an electronic device provided by an embodiment of the application. detailed description

In the prior art, the flow log of the Android system outputs information in business processing through the log system. For example, the log output format of the Android system includes timestamp, process ID, thread ID, level, and content. The output log information includes different businesses, different processes, and different threads, so it is difficult to distinguish and extract parts related to its own business. It can only be distinguished manually. For example, the part marked by the black dot shown in Figure 1 is the part that is manually marked and related to its own business. visible, The information output by the existing flow log may involve cross-process or cross-thread call relationships. If you want to obtain the call link information of a certain business, you rely on manual distinction, and failure analysis depends entirely on the developer's business capabilities and code familiarity. degree.

Similarly, the current performance tracing (systrace) log of the Android system also has similar problems to the flow log. The systrace log can only provide the relationship between the various layers of a thread, and it cannot provide the relationship between the cross-process or cross-thread call processing. For example, a timeout operation may involve cross-process or cross-thread calls. If the cause of the timeout is to be found, it is completely dependent on the developer's business ability. Obviously, this is time-consuming and labor-intensive, and the efficiency of problem solving is low.

In order to solve the above problem, the embodiment of the present application provides a method for generating log information. The method is mainly executed by an electronic device. When the electronic device receives a user's first operation, it responds to the first operation. At this time, the electronic device will The unique tracking identifier corresponding to the service is automatically generated, and this tracking identifier will be transmitted in the entire call link of the service. In this way, the electronic device can store the tracking identifier in each call link. In the call record of each thread of the process, log information including the tracking identifier is generated. Therefore, developers can obtain log information related to the business by searching for the tracking identifier, and analyze the cause of the failure.

For example, when the mobile phone detects a user's touch operation on the camera control in the camera application, it will respond to the touch operation, that is, add force at the start of the camera service corresponding to the control P—a unique tracking identifier Then, the tracking identifier will be passed down to the framework layer and the driver layer, and finally log information corresponding to the tracking identifier can be generated. Assuming that the mobile phone freezes when responding to the operation of taking a picture at this time, the developer can quickly locate the time-consuming thread by calling the log information corresponding to the tracking mark, thereby locating the cause of the failure. .

The log information generation method provided by the embodiment of the present application can be applied to the scenario shown in FIG. 2. In FIG. 2, when the user performs an operation on the electronic device 100, the electronic device generates a log, which includes log information corresponding to the tracking identifier, and then the electronic device can be uploaded to the cloud through the communication network, and then the developer operates the terminal device 200 from The cloud obtains the log of the electronic device, obtains the log information of the target business through the tracking identifier, and analyzes the cause of the failure. In addition, the electronic device 100 and the terminal device 200 may also be directly connected through the development tool, that is, the terminal device 200 directly obtains the log information of the electronic device 100 through the development tool, analyzes it, and obtains the cause of the failure.

In some embodiments of the present application, the electronic device 100 shown in FIG. 2 may be a portable electronic device that also includes other functions such as a personal digital assistant and/or a music player function, such as a mobile phone, a tablet computer, and a wireless communication function. Wearable devices (such as smart watches), etc. Exemplary embodiments of portable electronic devices include but are not limited to portable electronic devices equipped with iOS®, android®, microsoft® or other operating systems. The terminal device 200 may be a personal computer.

Taking the electronic device as a mobile phone as an example, FIG. 3 shows a schematic structural diagram of the mobile phone 100.

The mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a USB interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, and a wireless communication module 160, Audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and SIM card interface 195, etc.

It can be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may include more or fewer components than shown, or combine certain components, or disassemble certain components, or arrange different components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and/or neural network processor (Neural-network Processing Unit, NPU), etc. Among them, different processing units may be independent devices, or may be integrated in one or more processors. The controller may be the nerve center and command center of the mobile phone 100. The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that the processor 110 has just used or used cyclically. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.

The processor 110 may run the log information generation method provided in the embodiment of the present application to generate log information corresponding to the tracking identifier. When the processor 110 integrates different devices, such as integrated CPU and GI^U, the CPU and GPU can cooperate to execute the method provided in the embodiment of the present application, for example, some algorithms are executed by the CPU, and another part of the algorithms are executed by the GPU to obtain faster The processing efficiency.

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can use liquid crystal display (LCD), organic light-emitting diode (OLED), active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode). Emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diodes (QLED), etc. In some embodiments, the mobile phone 100 may include one or N display screens 194, and N is a positive integer greater than one.

In the embodiment of the present application, the display screen 194 receives a user's touch operation, and in response to the touch operation, the processor 110 adds a unique tracking identifier corresponding to the service at the service start entry.

Camera 193 (front camera or rear camera, or a camera can be used as a front camera or a rear camera) for capturing still images or videos. Generally, the camera 193 may include a photosensitive element such as a lens group and an image sensor, where the lens group includes a plurality of lenses (convex lens or concave lens) for collecting light signals reflected by the object to be photographed, and transmitting the collected light signals to the image sensor . The image sensor generates an original image of the object to be photographed according to the light signal.

The internal memory 121 may be used to store computer executable program code, where the executable program code includes instructions. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the storage program area can store codes of the operating system and application programs (such as camera applications, WeChat applications, etc.). The data storage area can store data created during the use of the mobile phone 100 (such as images and videos captured by a camera application) and the like.

The internal memory 121 can also store the code of the anti-mistouch algorithm provided in the embodiment of the present application. When the code of the anti-mistouch algorithm stored in the internal memory 121 is run by the processor 110, the touch operation during the folding or unfolding process can be shielded.

In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like.

Of course, the code of the anti-mistouch algorithm provided in the embodiment of the present application can also be stored in an external memory. In this case, the processor 110 can run the code of the anti-mistouch algorithm stored in the external memory through the external memory interface 120, so as to realize the shielding of the touch operation during the folding or unfolding process.

Wherein, the sensor module 180 may include a gyroscope sensor, an acceleration sensor, a proximity sensor, a fingerprint sensor, a touch sensor, a hinge sensor, etc. Of course, the mobile phone 100 may also include other sensors, such as a temperature sensor, a pressure sensor, a distance sensor, and a magnetic sensor. , Ambient light sensor, air pressure sensor, bone conduction sensor, etc., X is not shown in the figure

Exemplarily, the display screen 194 of the mobile phone 100 displays a main interface, and the main interface includes icons of multiple applications (such as a camera application, a Google app, etc.). The user clicks the icon of the camera application in the main interface through the touch sensor 180K, triggers the processor 110 to start the camera application, and turns on the camera 193. The display screen 194 displays the interface of the camera application, such as the viewfinder interface.

The wireless communication function of the mobile phone 100 can be realized by the antenna 1, the antenna 2, the mobile communication module 151, the wireless communication module 152, the modem processor, and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be multiplexed as a diversity antenna for wireless LAN. In other embodiments, the antenna can be used in combination with a tuning switch.

The mobile communication module 151 can provide a wireless communication solution including 2G/3G/4G/5G and the like applied to the terminal device 100. The mobile communication module 151 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 151 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering and amplifying the received electromagnetic waves, and then transmitting them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 151 may be provided in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 151 and at least part of the modules of the processor 110 may be provided in the same device.

The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Then the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs sound signals through audio equipment (not limited to speakers 170A, receiver 170B, etc.), or displays images or videos through the display 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 152 can provide applications on the terminal device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 152 may be one or more devices integrating at least one communication processing module. The wireless communication module 152 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 152 can also receive the signal to be sent from the processor 110, perform frequency modulation, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In addition, the mobile phone 100 can implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone interface 170D, and an application processor. For example, music playback, recording, etc. The mobile phone 100 can receive key 190 input, and generate key signal input related to the user settings and function control of the mobile phone 100. The mobile phone 100 can use the motor 191 to generate a vibration notification (for example, an incoming call vibration notification). The indicator 192 in the mobile phone 100 may be an indicator light, which may be used to indicate a charging state, a change in power level, and may also be used to indicate a message, a missed call, a notification, and the like. The SIM card interface 195 in the mobile phone 100 is used to connect to the SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the mobile phone 100.

It should be understood that, in actual applications, the mobile phone 100 may include more or less components than those shown in FIG. 1, which is not limited in the embodiment of the present application. The mobile phone software system can adopt a layered architecture, event-driven architecture, micro-core architecture, micro-service architecture, or cloud architecture. The embodiment of the present invention takes a layered Android system as an example to illustrate the software structure of a mobile phone.

The embodiment of the present application takes an Android system with a layered architecture as an example to exemplarily illustrate the software structure of the electronic device 100. FIG. 4 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application.

The layered architecture divides the software into thousands of layers, and each layer has a clear role and division of labor. Communication between layers through software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

The application layer can include a series of application packages.

As shown in Figure 4, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and so on.

The application framework layer provides an application programming interface (API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 4, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and so on.

The window manager is used to manage window programs. The window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.

The content provider is used to store and retrieve data, and make these data accessible to applications. The data may include video, image, audio, dialed and received calls, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, and so on. The view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a short message notification icon may include a view displaying text and a view displaying pictures.

The phone manager is used to provide the communication function of the mobile phone. For example, the management of call status (including connected, hang-up, etc.) X resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files and so on.

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and it can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify that the download is complete, message reminders, and so on. The notification manager can also be a notification that appears in the status bar at the top of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, text messages are displayed in the status bar, prompt sounds are emitted, electronic devices vibrate, and indicator lights flash.

Android Runtime includes core libraries and virtual machines. Android runtime is responsible for the scheduling and management of the Android system. The core library consists of two parts: one part is the function functions that the java language needs to call, and the other part is the core library of Android. The application layer and the application framework layer run in a virtual machine. The virtual machine executes the java files in the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides a combination of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support multiple audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing.

The 2D graphics engine is a graphics engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

In order to achieve the purpose of tracking the call link, the embodiment of the application improves the Android operating system shown in FIG. 4, as shown in FIG. 5, a tracking for implementing the call link tracking function is added to the Android system. System (HwTrace). The HwTrace system provides interfaces in the application layer (App), the framework layer (Framework), the system library (Native) and the kernel layer (Kernel) to support the functions of starting and stopping the tracking of business processes. Then modify the current communication mechanism (including binder, hwbinder, handler, socket, and system call). When the tracking is started, the communication mechanism of these processes, threads, user mode, and kernel mode is used to realize the transmission of the trace identification.

As shown in FIG. 5, the embodiment of the present application improves the existing communication mechanism. The improved modules mainly involve the message (message java) of the Framework layer, the cross-process communication library (Binder lib) of the Native layer and the message and Kernel layer. In addition, the tracking system has a Java language tracking system library (HwTrace lib) in Framework, a C/C++ language tracking system library (HwTrace lib) in Native, and a tracking system library (HwTrace lib) in the kernel layer. Kernel language tracking system library (HwTrace lib). Based on the improved Android operating system shown in Figure 5, the following embodiments of the application will combine the accompanying drawings and application scenarios to introduce the log information generation method provided by the embodiments of the application in detail The following embodiments can all be implemented in the electronic device 100 having the above hardware structure.

Referring to FIG. 6, the flow of a method for generating log information provided by an embodiment of the present application is exemplarily shown, and the method is executed by an electronic device.

Step 301: The electronic device receives the user's first operation, and in response to the first operation, the electronic device generates a unique tracking identifier corresponding to the service, and transmits the tracking identifier in the entire invocation link of the service.

Wherein, the first operation may be a touch operation, or a voice command, etc. The entire call link includes at least one process, and the at least one process includes at least one thread. When the call link includes more than two processes, then the call link includes cross-process calls and cross-thread calls.

Step 302: The electronic device stores the tracking identifier in the call record of each thread of each process of the call link, and generates log information including the tracking identifier.

For example, the log output format includes timestamp, process ID, thread ID, level, trace ID and content, and each piece of information in the final output log includes a trace ID.

For example, when the mobile phone detects the user's touch operation on the camera control in the camera application, it responds to the touch operation, that is, adds a unique tracking identifier to the entrance of the camera service corresponding to the control, Then the tracking identifier will be passed down to the framework layer and the driver layer, and finally log information corresponding to the tracking identifier can be generated. Since the call link may involve different layers and different communication mechanisms, in order to realize that the tracking identification can be accurately transmitted downwards, after the electronic device generates a unique tracking identification corresponding to the business, it writes the tracking identification to the first corresponding to the business entry. In the context of a thread, the tracking identifier is then transferred from the first thread to the second thread through a communication message, and the tracking identifier is written into the context of the second thread. If the second thread is not the last thread of the call link, repeat the communication message to transfer the trace identifier from the second thread to the third thread, and write the trace identifier into the context of the third thread until the call The last thread of the link. It should be noted that the first thread, the second thread, and the third thread may be threads of the same process or threads of different processes, and the call link may involve different communication methods. Step 303: Optionally, the electronic device generates a report that causes an abnormality in the call link according to the call timestamp of the thread, the call service name, and the call relationship with other threads in the log information.

Specifically, the electronic device calculates the calling time of each thread in the calling link according to the calling timestamp, and then generates a report that causes the calling link to be abnormal according to the calling time, calling relationship, and calling server name . For example, once a thread takes a long time, a report that the thread caused a timeout will be generated.

It can be seen that the embodiment of the application can realize that the calling link of a service carries a unique tracking identifier, so that the developer can quickly locate the time-consuming thread by calling the log information corresponding to the tracking identifier. , So as to locate the cause of the fault. It should be noted that the above-mentioned method of tracing the calling link through the tracking identifier is not limited to generating log information, and can also be used to generate other output information related to the business, for example, generating business information including the tracking identifier.

For different communication methods, the embodiments of this application provide specific delivery methods for the tracking identifier. It should be noted that TracelD will be used below to refer to the tracking identifier, which may be generated based on the identifier of the electronic device and the actual time of the user’s operation. The identification of the electronic device may be the identification of the processor.

First of all, the main communication methods, application scenarios, entities, TraceID transfer methods included in the Android system, as well as thread context setting and clearing conditions in the embodiment of the application are listed in Table 1.

Table 1

Specifically, for communication mode one and communication mode two in Table 1,

A complete Binder communication process is shown in Figure 7. Figure 7 includes the following steps:

Step 1. Process 1 sends the communication data to the Binder driver through the command word BC_Transaction. Step 2. The Binder driver forwards the communication data to process 2 for processing through the command word BR_Transaction.

Step 3. Process 2 sends the returned result back to the Binder driver through the command word BC_REPLY.

Step 4. The Binder driver forwards the returned result to the process through the command word BR_REPLY: L

For communication method 1, the basic method of transferring TracelD during binder communication is: (1) When process 1 sends data, write TmcelD into the context of the process; (2) when process 2 receives data, first save the context of the current thread Then, it obtains TracelD from the context, and writes the TracelD into the context of its own process; after the processing ends, it returns to the context of the current process.

Optionally, the first implementation mode: the lib layer of the binder and the driver cooperate to complete the transfer and removal

Specifically, the TraceID field is added to the lib layer data structure and the driver layer data structure of the binder, where the data structure includes binder_transaction_data, binder_transaction

1. Pass in the binder lib processing flow: BC_TRANSACTION/BC_REPLY is used to obtain TracelD from the thread context and write it into binder_transaction_data. BR_TRANS ACTION is used to save the current thread context first, and then set the TracelD in binder_transaction_data to the thread context; after processing, the thread context is restored.

2. Pass in the driver processing process of binder

BC_TRANSACTION/BC_REPLY/BC_TRANSACTION_SG/BC_REPLY_SG, used to realize the TracelD in the lib layer binder_transaction_data, save it in the driver layer binder_transaction.

BR_TRANSACTION/BR_REPLY is used to save TraceID in the binder_transaction of the driver layer to binder_transaction_data in the lib layer.

Optionally, the second way to implement: complete transfer and clearing in the driver

Add the TracelD field to the binder_transaction data structure of the driver layer of the binder.

Pass in the driver processing flow of binder:

BC_TRANSACTION/BC_REPLY/BC_TRANSACTION_SG/BC_REPLY_SG are used to obtain TraceID from the thread context corresponding to the system call and save it in binder_transaction.

BR_TRANSACTION/BR_REPLY is used to set TraceID in binder_transaction to the thread context corresponding to the system call.

Clear thread context information in the driver processing flow of binder:

BR_TRANSACTION_COMPLETE, used to clear the TraceID in the thread context corresponding to the system call (among which, oneway does not clear X

It should be noted that, because the second implementation method needs to support TracelD that accesses the thread context in the kernel mode and transfer, if the other process is not associated with the TracelD space, kernel allocation and association are required, but the second implementation method cannot achieve kernel allocation and association. Therefore, the first implementation can be preferred. For the second communication method, the transmission method of the tracking mark is the same as the first communication method.

Communication mode 3 for Table 1

Handle communication is based on the producer-consumer model. The basic way to pass TracelD in the handle communication process is: before message sending: write the data in the thread context into the message; before message processing: set the data in the message to the thread In context; after message processing: clear thread context

Among them, handle communication needs to be processed in Java and C layer:

For the Java layer, as shown in Figure 8, the first step is to add a TracelD field to the message class. In the second step, when the message is sent to the queue (MessageQueue), the thread context TracelD is written into the msg message. The third step, news Process the dispatchHandler entry and write TracelD in the message to the thread context. The fourth step, message processing enqueuepost exit, clear thread context TracelD.

For the C layer, in the first step, the TraceID field is added to the structure struct MessageEnvelope; in the second step, in the message sending Looper::sendMessageAtTime, the thread context TraceID is written into the messageEnvelope message. The third step, before the message processing handler->handleMessage (message), write TraceID in the message into the thread context. In the fourth step, after the message processing handler->handleMessage (message), the thread context TraceID is cleared.

For communication method four in Table 1

The basic way to pass TracelD in the socket communication process is: before message sending: write the data in the thread context into the socket sending message; before message processing: set the data in the socket message to the thread context; after message processing: Clear the context of the thread.

It should be noted that various calls may be involved in the process of TracelD transmission, such as B inder synchronous call, B inder synchronous call, Hwbinder synchronous call, Binder asynchronous call, Binder synchronous call in callee processing, and msg asynchronous call in Callee processing. deal with.

In the following embodiments of the present application, the specific process of the log information generation method is further described in detail in conjunction with the process synchronization invocation process shown in FIG. 9. The specific process of the method process may include:

Step a: Start call chain tracking in a certain business process of the application, generate TraceID according to the combination of CPUID and timestamp, and set it in the thread context (tls).

In step b, the process in the process synchronously calls other processes through the command word binder transact.

Step c: The process sending side obtains the current TraceID from the thread context, and writes the TraceID into the context. Step d, carry TraceID in the BC_TRANSACTION/BR_TRANSATION transfer of the binder message. Step e: Thread 1 of the system service (that is, the Binder receiving side) obtains TraceID from the data structure, and sets the passed TraceID to the current thread context, and processes it through the command word binder onTransact.

Step f, the thread 1 serviced by the system returns the result through the command word BC_REPLY, and then clears TraceID in the thread context.

In step g, the App side continues processing until the Trace call chain tracing ends, and the TraceID in the thread context is cleared. In summary, the embodiment of the application can realize the transfer of TracelD in the Android communication mechanism (binder, hwbinder, message, socket, syscall, etc.), and can realize high-performance access based on thread context technology, that is, save TracelD in process processing To the thread context, the relevant output information can be obtained from the thread context and saved in the content. Therefore, the embodiment of the present application can realize the transmission of TraceID in the call link.

Further, after the tracking identifier is transferred in the call link, the electronic device obtains the tracking identifier from the context of each thread, converts the tracking identifier into a character string, writes it into the print information, and generates log information. In addition, the electronic device The log information corresponding to the tracking identifier is filtered out.

Specifically, for the flow log, in order to obtain the log information corresponding to the tracking mark through the tracking mark, it is necessary to first associate the flow log with the tracking system. The correlation method is: in the user mode log printing interface, determine the current thread context Whether TracelD is valid in the middle, whether to set the user mode log associated switch, if so, convert TracelD into a string and insert it into the print information. Among them, the flow log is mainly modified at the bottom level, which has less impact on performance. The bottom layer of the current log is written to logd through sockets, using the vector write writev interface (multiple buffers), so when writing, a TracelD string buffer is added before the message string buffer, so that the socket on the receiving side is automatically spliced. Regarding the kernel log, in order to obtain the log information corresponding to the tracking identifier through the tracking identifier, it is also necessary to associate the kernel log with the tracking system first. The correlation method is: in the kernel mode printing interface, it is determined that the current system call context ( Non-interrupting context), whether TracelD in the current thread context is valid, whether to set the kernel state log correlation switch, if so, convert TracelD into a string and insert it into the print information. Among them, the kernel mode log is uniformly modified in the underlying interface, mainly involving the modification of the printk function.

For the performance trace log (systrace), systrace obtains TracelD from the thread context, and connects the systrace of the entire business process through TracelD. In order to obtain the log information corresponding to the tracking identifier through the tracking identifier, it is necessary to first associate systrace with the tracking system. The association method is: In user mode systrace printing, determine whether TracelD is valid in the current thread context and whether to set systrace association Switch, if yes, add TracelD parameters to the output content according to the systrace format specification. Among them, the systrace output is modified as far as possible in the bottom layer, while considering the efficiency. The current systarce output is written to the /sys/kernel/debug/tracing/trace_marker interface at the bottom layer through multiple atrace interfaces, and the WRITE_MSG macro interface is used to convert the parameters to strings. Therefore, the output is in accordance with the format required by systrace, and TracelD is added as an addition The args parameter is inserted at the end of the string.

It can be seen that the use of the call link tracking technology provided by the embodiment of the present application can solve the problem of log output information correlation in the business process. As shown in Figure 10, the black shadow corresponds to TraceID93921d2463. The electronic device can automatically identify the log output information of a complete business process by searching for the TracelD, that is, through the TracelD, a cross-process, cross-thread, and multi-level The output information of the business process is filtered and extracted. Reduce the ability to rely on developers, improve the efficiency of fault analysis, and quickly locate faults.

In addition, using the call link tracking technology provided by the embodiments of the present application can solve the problem of systrace output information correlation in the business process. In Figure 11a, the UI Thread thread binder calls transact[35] to increase the Args parameter identifier "3fOfcalal3", which is the same as the Args parameter of the Binder: 1060_4 thread in Figure lib, which directly clarifies the cross-process binder calling relationship. That is, it can be determined through TracelD that the main time-consuming call of the UI Thread thread binder is due to the blocking of the called process. The embodiment of the present application also provides a method and device for generating log information. As shown in FIG. 12, the device includes a receiving module 1201 and a processing module 1202.

Wherein, in a possible embodiment, the receiving module 1201 is configured to receive the first operation of the user. The relevant content involved in the method embodiments in Figure 6 to Figure lib can all be quoted from the functional description of the receiving module 1101, which will not be repeated here.

The processing module 1202 is configured to, in response to the first operation, add a unique tracking identifier corresponding to the service at the service start entry, and transfer the tracking identifier in the entire invocation link of the service, where The entire call link includes at least one process, and the at least one process includes at least one thread; and the trace identifier is stored in the call record of each thread of each process of the call link to generate Describe the log information of the tracking mark. The related content involved in the method embodiments of Figure 6 to Figure lib can all be quoted from the functional description of the processing module 1202, which will not be repeated here.

It should be noted that the switching device of the application icon of the electronic device has the function of realizing the electronic device in the above method design. These unit modules can be implemented by hardware in the terminal, or can be implemented by hardware in the terminal executing corresponding software, which is not limited in the embodiment of the present application.

It can be seen that the embodiment of the present application can generate log information including the tracking identifier, which is convenient for developers to extract information related to problems, reduces the ability requirements for developers, and improves problem solving efficiency.

An embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium includes a computer program. When the computer program runs on an electronic device, the electronic device executes any one of the aforementioned information processing methods. A possible realization.

The embodiments of the present application also provide a computer program product, which when the computer program product runs on an electronic device, causes the electronic device to execute any one possible implementation of the foregoing information processing method.

In other embodiments of the present application, the embodiments of the present application disclose an electronic device. As shown in FIG. 13, the electronic device may include: a processor 1301; a memory 1302; and one or more computer programs 1303, as described above Each device can be connected through one or more communication buses 1304.

The one or more computer programs 1303 are stored in the above-mentioned memory 1302 and are configured to be invoked and executed by the processor 1301, and the one or more computer programs 1303 include instructions, and the above-mentioned instructions can be used for execution as shown in FIG. 6 to FIG. Each step in the corresponding embodiment.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and clarity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned functions can be changed as required. The allocation is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the above-described system, device, and unit, reference may be made to the corresponding process in the foregoing method embodiment, which is not repeated here.

The functional units in the various embodiments of the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be realized in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage The medium includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

The above are only specific implementations of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of the present application shall be covered in this application. Within the protection scope of the application embodiments. Therefore, the protection scope of the embodiments of the present application should be subject to the protection scope of the claims.

Claims

1. A method for generating log information applied to an electronic device, characterized in that the method includes:

Receive the user's first operation;

In response to the first operation, a unique tracking identifier corresponding to the service is generated, and the tracking identifier is transmitted in the entire invocation link of the service, where the entire invocation link includes the information used to execute the service At least one process, where the at least one process includes at least one thread;

The tracking identifier is stored in the call record of each thread of each process of the call link, and log information including the tracking identifier is generated.

2. The method according to claim 1, wherein storing the tracking identifier in the call record of each thread of each process of the call link comprises:

The character string obtained by the conversion of the tracking identifier is stored in the call record of each thread of each process of the call link, and log information including the tracking identifier is generated.

3. The method according to claim 2, wherein the electronic device generates a unique tracking identifier corresponding to the service, and transmitting the tracking identifier in the entire invocation link, comprising:

Generating a unique tracking identifier corresponding to the service, and writing the tracking identifier into the context of the first thread corresponding to the service start entry;

Transfer the tracking identifier from the first thread to the second thread through a communication message, and write the tracking identifier into the context of the second thread;

If the second thread is not the last thread of the call link, repeat the execution of transferring the trace identifier from the second thread to the third thread through a communication message, and write the trace identifier to all threads. In the context of the third thread, until the tracking identifier is written into the context of the last thread of the call link.

4. The method according to claim 2 or 3, wherein the electronic device stores the character string converted from the tracking identifier in the call record of each process of the call link, and generates The log information of the tracking mark includes:

Acquiring the tracking identifier from the context of each thread of the call link;

The character string obtained by the conversion of the tracking identifier is written into the call record of each thread in each process of the call link, and log information including the tracking identifier is generated.

5. The method according to claim 4, wherein the log information includes at least one of a running log, a kernel log, and a performance tracking log.

6. The method according to any one of claims 1 to 5, wherein the log information includes the call timestamp of the thread, the call service name, and the call relationship of other threads;

The method also includes:

Calculating the calling time of each thread in the calling link according to the calling timestamp;

According to the calling time, the calling relationship and the calling server name, a report that causes the abnormality of the calling link is generated.

7. The method according to any one of claims 1 to 6, wherein the tracking identifier is generated based on the identifier of the electronic device and the occurrence time of the first operation.

8. A log information generating device, characterized in that the device includes:

A receiving module, configured to receive the first operation of the user;

The processing module is configured to generate a unique tracking identifier corresponding to the service in response to the first operation, and in the The tracking identifier is transferred in the entire invocation link of the service, where the entire invocation link includes at least one process for executing the service, and the at least one process includes at least one thread;

The generating module is configured to store the tracking identifier in the call record of each thread of each process of the call link, and generate log information including the tracking identifier.

9. The device according to claim 8, wherein the processing module is specifically configured to:

10. The device according to claim 9, wherein the processing module is specifically configured to:

11. The device according to claim 9 or 10, wherein the generating module is specifically configured to: obtain the tracking identifier from the context of each thread of the call link;

12. The device according to claim 11, wherein the log information includes at least one of a running log, a kernel log, and a performance tracking log.

13. The device according to any one of claims 8 to 12, wherein the log information includes thread call timestamp, call service name, and call relationship of other threads;

The device also includes:

14. The apparatus according to any one of claims 9 to 13, wherein the tracking identifier is generated based on the identifier of the electronic device and the occurrence time of the first operation.

15. An electronic device, comprising one or more processors and one or more memories; where the one or more memories are connected to the one or more processors, and the one or more memories Used to store computer program code, where the computer program code includes computer instructions, and when the one or more processors execute the computer instructions, the electronic device executes the log according to any one of claims 1 to 7 Information generation method.

16. A computer-readable storage medium, wherein the computer-readable storage medium includes a computer program, which when the computer program runs on an electronic device, causes the electronic device to execute any one of claims 1 to 7 The method for generating log information.