CN103577310A - Method and device for recording software debugging logs - Google Patents
Method and device for recording software debugging logs Download PDFInfo
- Publication number
- CN103577310A CN103577310A CN201210259391.XA CN201210259391A CN103577310A CN 103577310 A CN103577310 A CN 103577310A CN 201210259391 A CN201210259391 A CN 201210259391A CN 103577310 A CN103577310 A CN 103577310A
- Authority
- CN
- China
- Prior art keywords
- thread
- log
- name
- journal file
- software debugging
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a device for recording software debugging logs. The method comprises the steps of starting one or more thread, wherein every thread comprises a thread identifier; setting a thread name of every thread and establishing a corresponding table of the thread names and the thread identifiers; establishing a plurality of log files, corresponding every thread to one of the log files; obtaining the current thread identifier and searching the thread name which is corresponding to the current thread identifier according to the corresponding table; writing log information produced by execution of the current thread into the log file which is corresponding o the current thread. Every thread comprises a corresponding log file name and accordingly an operator can understand the execution steps of the integral program conveniently by reviewing a plurality of log content. In addition, the operator can still understand which one of the threads is in case of errors in the execution process by reviewing the plurality of log files even if a module which is utilized by the plurality of threads is abnormal when one of the threads is executed.
Description
Technical field
The present invention relates to a kind of for computer software fields, espespecially a kind of method of logging software debugging log and device.
Background technology
Along with the fast development of computer technology, in people's life and work, by computing machine, use the demand of application software also increasing.Along with the scale of application software constantly expands, in order to allow the more efficient running of computing machine, present software has generally adopted multithreading.Yet the scale of software is larger, the complexity of debugging is also more and more higher.So inquire about, follow the trail of and analyze for the ease of operator in the future, system can produce daily record (log) to record behavior and the state of each thread operation.
Traditional software debugging daily record is all to carry out record according to software module, and by the log recording of same module or a plurality of modules among identical file.Yet, in debugging (debugging) process of software, the output quantity of daily record is quite huge and difficult reading often, once in order to check on the execution step of whole program, opening a plurality of journal file contrasts checks, just can check on, accidentally can miss the detail of issue track.And extremely conventionally all the appearing in a certain thread of multi-thread software, huge daily record amount is unfavorable problem of searching certain function or module also.In addition, because the log recording of a plurality of modules is among same journal file, it is abnormal that the module that all will call for a plurality of threads is also difficult for judging from described journal file that rapidly which module occurs when the execution thread.
Therefore, be necessary to provide a kind of method and device of logging software debugging log, to solve the existing problem of prior art.
Summary of the invention
The method and the device that the object of this invention is to provide a kind of logging software debugging log, can easily see the step of program execution clearly and facilitate positioning software abnormal, to solve the problem of prior art.
For reaching aforementioned object of the present invention, the invention provides a kind of method of logging software debugging log, comprise the steps: to carry out a debugged program, described debugged program comprises at least one thread, and each thread has a thread identifier; The thread name of each thread is set, and sets up the corresponding table of each thread name and each thread identifier; Set up at least one journal file, each thread corresponds to a journal file; Obtain current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table; And the log information of carrying out described current thread generation is write in journal file corresponding to described current thread.
According to one embodiment of the invention, described log information comprises and starts the time of thread, the module name that uses described thread and function name.
According to one embodiment of the invention, described log information comprises that sequentially record starts the time of described thread each time.
According to one embodiment of the invention, the filename of each journal file is identical with corresponding thread name.
According to one embodiment of the invention, after the log information of carrying out described current thread generation is write to the step in journal file corresponding to described current thread, also comprise: when receiving a show log file request, according to described show log file request, show corresponding journal file.
Moreover the present invention provides again a kind of device of logging software debugging log, it comprises: processing unit, be used for carrying out a debugged program, and described debugged program comprises at least one thread, and each thread has a thread identifier; Unit is set up in daily record, is used for, when starting described at least one thread, setting up at least one journal file, and each thread corresponds to a journal file, and each thread has a thread identifier; Storage unit, is used for storing a corresponding table, and described corresponding table is used for recording the thread name of each thread and the corresponding relation of each thread identifier; And daily record writing unit, be used for obtaining current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table, and the log information of carrying out described current thread generation is write to journal file corresponding to described current thread.
According to one embodiment of the invention, described log information comprises and starts the time of thread, the module name that uses described thread and function name.
According to one embodiment of the invention, described log information comprises that sequentially record starts the time of described thread each time.
According to one embodiment of the invention, the filename of each journal file is identical with corresponding thread name.
According to one embodiment of the invention, separately comprise an output unit, be used for when receiving a show log file request, according to described show log file request, show corresponding journal file.
The present invention separately provides a kind of device of logging software debugging log, it comprises: module is set up in daily record, while being used at least one thread in Start-up and Adjustment program, set up at least one journal file, each thread corresponds to a journal file and each thread has a thread identifier; Corresponding table record module, is used for setting up the corresponding table of each thread name and each thread identifier; And daily record writing module, be used for obtaining current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table, and the log information of carrying out described current thread generation is write to journal file corresponding to described current thread.
According to one embodiment of the invention, described log information comprises and starts the time of thread, the module name that uses described thread and function name.
According to one embodiment of the invention, described log information comprises that sequentially record starts the time of described thread each time.
According to one embodiment of the invention, the filename of each journal file is identical with corresponding thread name.
Compared to prior art, the present invention proposes a kind ofly according to method and the device of thread logging software debugging log, can realize simple, software anomaly location efficiently.When starting due to each thread, all can produce corresponding journal file, set journal file name simultaneously and meet its thread name, so operator can just know that the daily record of consulting is to correspond to the performed content of which thread immediately by journal file name.In addition, abnormal even the module that a plurality of thread all will be used occurs when carrying out one of them thread, operator still can be easily by checking a plurality of daily records, and understanding is which thread makes a mistake in the process of implementation.Therefore the invention solves under traditional multi-thread environment, according to the daily record inconvenience of module records, read and cannot find fast that abnormal problem appears in which thread.
For foregoing of the present invention can be become apparent, preferred embodiment cited below particularly, and coordinate appended graphicly, be described in detail below:
Accompanying drawing explanation
Fig. 1 is the block schematic diagram of device of the logging software debugging log of one embodiment of the invention.
Fig. 2 is the process flow diagram of the method for logging software debugging log of the present invention.
Fig. 3 is the block schematic diagram of device of the logging software debugging log of another embodiment of the present invention.
Embodiment
Refer to Fig. 1, Fig. 1 is the block schematic diagram of device 10 of the logging software debugging log of one embodiment of the invention.Device 10 comprises a processing unit 12, a storage unit 14, an input interface 16, an output unit 18, daily record and sets up unit 20 and daily record writing unit 22.Device 10 can be personal computer (PC), mobile computer, Digital Television, other can software program for execution code electronic installation, or be built in the unit that hardware circuit, software unit or the soft and hardware of the electronic installations such as personal computer, mobile computer, Digital Television combine.
Next, daily record is set up unit 20 and is used for when each thread is activated, sets up at least one journal file and the journal file of generation is stored among storage unit 14.In the present embodiment, each thread corresponds to a journal file, preferred, and for ease of reading and analyzing, each journal file name can be consistent with the thread name of corresponding thread.For instance, if the thread name of thread B is HWDecoder, the journal file name of corresponding journal file B can be automatically made HWDecoder.log.When thread A is performed, unit 20 is set up in daily record can set up a journal file A identical with the thread name of thread A, and when thread B is performed, unit 20 is set up in daily record can set up a journal file B identical with the thread name of thread B.Storage unit 14 also can be used for storing a corresponding table 30.The content understanding that those skilled in the art also can disclose according to the present embodiment arrives, and journal file name can produce by other suitable naming rule, and for example numeral number or word are numbered orderly.
Corresponding table 30 is used for recording the thread name of each thread and the corresponding relation of each thread identifier.Because each thread can repeatedly be carried out at different time, when therefore thread is performed each time, daily record writing unit 22 can be used for obtaining the current corresponding thread identifier of thread that is performed, and by described corresponding table 30, search the thread name of corresponding current thread identifier, and write and be stored in storage unit 14 in the journal file corresponding to current thread carrying out log information that described current thread produces.Log information can be including but not limited to following content: start each time the time of thread, use the module name of described thread and function name etc.For instance, thread B at 3:00 when module C is carried out for the first time, unit 20 is set up in daily record can be according to the thread name HWDecoder of thread B, producing journal file name is the journal file B of HWDecoder.log, the simultaneously thread identifier of corresponding table 30 record thread B and the corresponding relation of journal file B, and set up the time of journal file, the log information that performed by module C and other is relevant all can be written among journal file B.Then, thread B at 5:00 when module D is carried out for the second time, daily record writing unit 22 can be used for obtaining the corresponding thread identifier of thread B, and by this thread identifier, by corresponding table 30, found out the journal file B of corresponding thread B, the time of again carrying out, the log information that performed by module D and other is relevant are written to journal file B.That is to say, no matter whether thread B is performed by same module, journal file B can, according to the time that thread B is performed each time, record relevant log information when thread B carries out each time.
Finally, when local side or long-range operator are during by input interface 16 input show log file request, the content of show log file request described in processing unit 12 meeting identifications, with the journal file of confirming to show, and the journal file that storage unit 14 is stored is sent to output unit 18, for example printer, screen etc., can print off by printer journal file, or be presented on screen, so that the state of operator's inquiry, tracking, analysis software debugging log.
See also Fig. 1 and Fig. 2, Fig. 2 is the process flow diagram of the method for logging software debugging log of the present invention.The method bag following steps of logging software debugging log of the present invention:
Step 202: carry out a debugged program, described debugged program comprises at least one thread, and each thread has a thread identifier.
In this step, operator carries out instruction by input interface 16 inputs, processing unit 12 is opened and carried out debugged program, and wherein said debugged program includes at least one thread, and each thread has a thread identifier.
Step 204: the thread name of each thread is set, and sets up the corresponding table 30 of each thread name and each thread identifier.
In this step, storage unit 14 can storage one corresponding table 30.Corresponding table 30 is for recording the thread name of each thread and the corresponding relation of each thread identifier.
Step 206: set up at least one journal file, each thread corresponds to a journal file.
In this step, when processing unit 12 starts a thread, can control in the lump daily record and set up unit 20 and set up a journal file, that is to say, when having a plurality of threads to be activated, can set up a plurality of journal files, and described a plurality of journal files are stored in to storage unit 14.Therefore operator can directly confirm from journal file name that described journal file is the operating state that records corresponding thread in the future.The content understanding that those skilled in the art also can disclose according to the present embodiment arrives, and journal file name can produce by other suitable naming rule, and for example numeral number or word are numbered orderly.
Step 208: obtain current thread identifier, and search the thread name of corresponding described current thread identifier by corresponding table 30.
After this step, when a certain thread is activated, processing unit 12 can first be obtained the current thread identifier that is just being activated thread, and then by corresponding table 30, searching current thread identifier searches corresponding thread name.
Step 210: the log information of carrying out described current thread generation is write in journal file corresponding to described current thread.
In this step, the log information that processing unit 12 control daily record writing units 22 produce execution current thread writes among journal file corresponding to current thread.Log information can be including but not limited to following content: start each time the time of thread, use the module name of described thread and function name etc.
Step 212: when receiving a show log file request, show corresponding journal file according to described show log file request.
After previous step 210, when receiving a show log file request from input interface 16, the content of show log file request described in processing unit 12 meeting identifications, with the journal file of confirming to show, and the journal file that storage unit 14 is stored is sent to output unit 18, so that the state of operator's inquiry, tracking, analysis software debugging log.
Refer to Fig. 3, Fig. 3 is the block schematic diagram of device 30 of the logging software debugging log of another embodiment of the present invention.In the present embodiment, installing 30 is that it comprises daily record and sets up module 32, corresponding table record module 34 and daily record writing module 36 according to the electronic installation of the counter program code running of programming.When daily record is set up module 32 and is used at least one thread in Start-up and Adjustment program, set up at least one journal file, each thread corresponds to a journal file and each thread has a thread identifier.Corresponding table record module 34 is used for setting up the corresponding table of each thread name and each thread identifier.Daily record writing module 36 is used for obtaining current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table, and the log information of carrying out described current thread generation is write to journal file corresponding to described current thread.
The present invention, according to method and the device of thread logging software debugging log, can realize simple, efficient software anomaly location.When starting due to each thread, all can produce corresponding journal file, set journal file name simultaneously and meet its thread name, so operator can just know that the daily record of consulting is to correspond to the performed content of which thread immediately by journal file name.In addition, abnormal even the module that a plurality of thread all will be used occurs when carrying out one of them thread, operator still can be easily by checking a plurality of daily records, and understanding is which thread makes a mistake in the process of implementation.Therefore the invention solves under traditional multi-thread environment, according to the daily record inconvenience of module records, read and cannot find fast that abnormal problem appears in which thread.
In sum; although the present invention discloses as above with preferred embodiment; but above-mentioned preferred embodiment is not in order to limit the present invention; those of ordinary skill in the art; within without departing from the spirit or scope of the invention; all can do various changes and retouching, so the scope that protection scope of the present invention defines with claim is as the criterion.
Claims (14)
1. a method for logging software debugging log, is characterized in that, comprises step:
Carry out a debugged program, described debugged program comprises at least one thread, and each thread has a thread identifier;
The thread name of each thread is set, and sets up the corresponding table of each thread name and each thread identifier;
Set up at least one journal file, each thread corresponds to a journal file;
Obtain current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table; And
The log information of carrying out described current thread generation is write in journal file corresponding to described current thread.
2. the method for logging software debugging log as claimed in claim 1, is characterized in that: described log information comprises the time that starts each time described thread, the module name that uses described thread and function name.
3. the method for logging software debugging log as claimed in claim 1 or 2, is characterized in that: described log information comprises that record sequentially starts the time of described thread each time.
4. the method for logging software debugging log as claimed in claim 1, is characterized in that: the filename of each journal file is identical with corresponding thread name.
5. the method for logging software debugging log as claimed in claim 1, it is characterized in that: after the log information of carrying out described current thread generation is write to the step in journal file corresponding to described current thread, also comprise: when receiving a show log file request, according to described show log file request, show corresponding journal file.
6. a device for logging software debugging log, is characterized in that, comprising:
Processing unit, is used for carrying out a debugged program, and described debugged program comprises at least one thread, and each thread has a thread identifier;
Unit is set up in daily record, is used for, when starting described at least one thread, setting up at least one journal file, and each thread corresponds to a journal file;
Storage unit, is used for storing a corresponding table, and described corresponding table is used for recording the thread name of each thread and the corresponding relation of each thread identifier; And
Daily record writing unit, is used for obtaining current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table, and the log information of carrying out described current thread generation is write to journal file corresponding to described current thread.
7. the device of logging software debugging log as claimed in claim 6, is characterized in that: described log information comprises and starts the time of thread, the module name that uses described thread and function name.
8. the device of the logging software debugging log as described in claim 6 or 7, is characterized in that: described log information comprises that record sequentially starts the time of described thread each time.
9. the device of logging software debugging log as claimed in claim 6, is characterized in that: the filename of each journal file is identical with corresponding thread name.
10. the device of logging software debugging log as claimed in claim 6, is characterized in that: separately comprise an output unit, be used for when receiving a show log file request, according to described show log file request, show corresponding journal file.
The device of 11. 1 kinds of logging software debugging logs, is characterized in that, comprising:
Module is set up in daily record, while being used at least one thread in Start-up and Adjustment program, sets up at least one journal file, and each thread corresponds to a journal file and each thread has a thread identifier;
Corresponding table record module, is used for setting up the corresponding table of each thread name and each thread identifier; And
Daily record writing module, is used for obtaining current thread identifier, and the thread name of searching corresponding described current thread identifier by described corresponding table, and the log information of carrying out described current thread generation is write to journal file corresponding to described current thread.
The device of 12. logging software debugging logs as claimed in claim 11, is characterized in that: described log information comprises and starts the time of thread, the module name that uses described thread and function name.
The device of 13. logging software debugging logs as described in claim 11 or 12, is characterized in that: described log information comprises that record sequentially starts the time of described thread each time.
The device of 14. logging software debugging logs as claimed in claim 11, is characterized in that: the filename of each journal file is identical with corresponding thread name.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210259391.XA CN103577310A (en) | 2012-07-20 | 2012-07-20 | Method and device for recording software debugging logs |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210259391.XA CN103577310A (en) | 2012-07-20 | 2012-07-20 | Method and device for recording software debugging logs |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103577310A true CN103577310A (en) | 2014-02-12 |
Family
ID=50049137
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210259391.XA Pending CN103577310A (en) | 2012-07-20 | 2012-07-20 | Method and device for recording software debugging logs |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103577310A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103984621A (en) * | 2014-04-01 | 2014-08-13 | 广州杰赛科技股份有限公司 | Method and system for separating log |
| CN105187241A (en) * | 2015-08-19 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Log recording method and system based on linux kernel |
| CN107656868A (en) * | 2017-09-18 | 2018-02-02 | 上海斐讯数据通信技术有限公司 | A kind of adjustment method and system that thread name is obtained using thread private data |
| CN108491300A (en) * | 2018-01-10 | 2018-09-04 | 北京掌阔移动传媒科技有限公司 | One kind being based on distributed log processing system |
| CN108563503A (en) * | 2018-01-02 | 2018-09-21 | 郑州云海信息技术有限公司 | A kind of stream data recording method and data flow for program test records system |
| CN109643273A (en) * | 2016-08-31 | 2019-04-16 | 微软技术许可有限责任公司 | The program tracking debugged and analyzed for time travel |
| CN109918178A (en) * | 2019-03-06 | 2019-06-21 | 恒生电子股份有限公司 | Affairs submit method and relevant apparatus |
| CN112540808A (en) * | 2019-09-23 | 2021-03-23 | 腾讯科技（深圳）有限公司 | Method for recording program behavior level calling relation and related equipment |
| US11126536B2 (en) | 2016-10-20 | 2021-09-21 | Microsoft Technology Licensing, Llc | Facilitating recording a trace file of code execution using index bits in a processor cache |
| US11138092B2 (en) | 2016-08-31 | 2021-10-05 | Microsoft Technology Licensing, Llc | Cache-based tracing for time travel debugging and analysis |
| US11194696B2 (en) | 2016-10-20 | 2021-12-07 | Microsoft Technology Licensing, Llc | Recording a trace of code execution using reserved cache lines in a cache |
| CN115328755A (en) * | 2022-10-11 | 2022-11-11 | 中化现代农业有限公司 | Concurrent log recording method and system |
| US11915028B2 (en) | 2017-04-01 | 2024-02-27 | Microsoft Technology Licensing, Llc | Virtual machine execution tracing |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101087210A (en) * | 2007-05-22 | 2007-12-12 | 网御神州科技（北京）有限公司 | High-performance Syslog processing and storage method |
| CN101667113A (en) * | 2008-09-02 | 2010-03-10 | 阿里巴巴集团控股有限公司 | Method and device for multi-thread log entry |
| CN102331991A (en) * | 2011-03-18 | 2012-01-25 | 北京神州数码思特奇信息技术股份有限公司 | Method for storing journals in asynchronous mode on basis of JAVA language |
-
2012
- 2012-07-20 CN CN201210259391.XA patent/CN103577310A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101087210A (en) * | 2007-05-22 | 2007-12-12 | 网御神州科技（北京）有限公司 | High-performance Syslog processing and storage method |
| CN101667113A (en) * | 2008-09-02 | 2010-03-10 | 阿里巴巴集团控股有限公司 | Method and device for multi-thread log entry |
| CN102331991A (en) * | 2011-03-18 | 2012-01-25 | 北京神州数码思特奇信息技术股份有限公司 | Method for storing journals in asynchronous mode on basis of JAVA language |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103984621B (en) * | 2014-04-01 | 2017-08-11 | 广州杰赛科技股份有限公司 | log separation method and system |
| CN103984621A (en) * | 2014-04-01 | 2014-08-13 | 广州杰赛科技股份有限公司 | Method and system for separating log |
| CN105187241A (en) * | 2015-08-19 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | Log recording method and system based on linux kernel |
| US11138092B2 (en) | 2016-08-31 | 2021-10-05 | Microsoft Technology Licensing, Llc | Cache-based tracing for time travel debugging and analysis |
| CN109643273A (en) * | 2016-08-31 | 2019-04-16 | 微软技术许可有限责任公司 | The program tracking debugged and analyzed for time travel |
| CN109643273B (en) * | 2016-08-31 | 2022-02-01 | 微软技术许可有限责任公司 | Computer system, method, hardware storage device for recording playable traces |
| US11194696B2 (en) | 2016-10-20 | 2021-12-07 | Microsoft Technology Licensing, Llc | Recording a trace of code execution using reserved cache lines in a cache |
| US11126536B2 (en) | 2016-10-20 | 2021-09-21 | Microsoft Technology Licensing, Llc | Facilitating recording a trace file of code execution using index bits in a processor cache |
| US11915028B2 (en) | 2017-04-01 | 2024-02-27 | Microsoft Technology Licensing, Llc | Virtual machine execution tracing |
| CN107656868A (en) * | 2017-09-18 | 2018-02-02 | 上海斐讯数据通信技术有限公司 | A kind of adjustment method and system that thread name is obtained using thread private data |
| CN108563503A (en) * | 2018-01-02 | 2018-09-21 | 郑州云海信息技术有限公司 | A kind of stream data recording method and data flow for program test records system |
| CN108491300A (en) * | 2018-01-10 | 2018-09-04 | 北京掌阔移动传媒科技有限公司 | One kind being based on distributed log processing system |
| CN109918178B (en) * | 2019-03-06 | 2021-04-30 | 恒生电子股份有限公司 | Transaction submitting method and related device |
| CN109918178A (en) * | 2019-03-06 | 2019-06-21 | 恒生电子股份有限公司 | Affairs submit method and relevant apparatus |
| CN112540808A (en) * | 2019-09-23 | 2021-03-23 | 腾讯科技（深圳）有限公司 | Method for recording program behavior level calling relation and related equipment |
| CN112540808B (en) * | 2019-09-23 | 2023-10-13 | 腾讯科技（深圳）有限公司 | Recording method of program behavior hierarchy call relationship and related equipment |
| CN115328755A (en) * | 2022-10-11 | 2022-11-11 | 中化现代农业有限公司 | Concurrent log recording method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103577310A (en) | Method and device for recording software debugging logs | |
| CN107273280B (en) | Log processing method and device, electronic equipment and storage medium | |
| CN109240886B (en) | Exception handling method, exception handling device, computer equipment and storage medium | |
| US9356966B2 (en) | System and method to provide management of test data at various lifecycle stages | |
| US9645911B2 (en) | System and method for debugging firmware/software by generating trace data | |
| CN105074671A (en) | Method and system for detecting concurrency programming errors in kernel modules and device drivers | |
| CN110737594A (en) | Database standard conformance testing method and device for automatically generating test cases | |
| CN103294588A (en) | Memory detecting system and method | |
| CN110597704B (en) | Pressure test method, device, server and medium for application program | |
| US11003570B2 (en) | Performing a mirror test for localization testing | |
| CN105468511A (en) | Web page script error positioning method and apparatus | |
| CN110908894A (en) | Visual report tool automatic testing method and device based on vuex | |
| CN101425070B (en) | Deadlock positioning method, deadlock positioning device and data system | |
| CN108446224A (en) | The method for analyzing performance, storage medium of application program on mobile terminal | |
| CN112162954B (en) | User operation log generation and path positioning method, device, equipment and medium | |
| CN107656868B (en) | Debugging method and system for acquiring thread name by using thread private data | |
| US20110224939A1 (en) | Integrated tool for persisting development environment test scenario information | |
| CN105607957B (en) | A kind of data acquisition analysis system based on OPC DA | |
| CN115291938A (en) | Component configuration method and system for electronic evidence analysis | |
| CN109062797B (en) | Method and device for generating information | |
| US9508062B2 (en) | Problem management record profiling | |
| CN113760696A (en) | Program problem positioning method and device, electronic equipment and storage medium | |
| CN110781092A (en) | Script testing method, device, terminal and storage medium | |
| CN116610656B (en) | Portable cross-network data acquisition method and device | |
| CN113360454B (en) | Memory snapshot file compression and decompression method and related device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140212 |